Git Product home page Git Product logo

microsoft / seccon-framework Goto Github PK

View Code? Open in Web Editor NEW
275.0 38.0 47.0 479 KB

Security configuration is complex. With thousands of group policies available in Windows, choosing the “best” setting is difficult. It’s not always obvious which permutations of policies are required to implement a complete scenario, and there are often unintended consequences of some security lockdowns. The SECCON Baselines divide configuration into Productivity Devices and Privileged Access Workstations. This document will focus on Productivity Devices (SECCON 5, 4, and 3). Microsoft’s current guidance on Privileged Access Workstations can be found at http://aka.ms/cyberpaw and as part of the Securing Privileged Access roadmap found at http://aka.ms/privsec.

License: Creative Commons Attribution 4.0 International

seccon-framework's Introduction

Get Started

Learn about the security configuration framework. We welcome your feedback and contributions.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Legal Notices

Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.

Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.

Privacy information can be found at https://privacy.microsoft.com/en-us/

Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.

seccon-framework's People

Contributors

amitairottem avatar appcompatguy avatar dansimp avatar justinha avatar microsoft-github-policy-service[bot] avatar microsoftopensource avatar msftgits avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

seccon-framework's Issues

Enterprise Basic Security configuration and the Windows Security baseline

Hi,

currently, I'm working on security hardening of windows 10 machines, I checked the Windows Security Baseline https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-security-baselines and come over this repo while reading this article https://www.microsoft.com/security/blog/2019/04/11/introducing-the-security-configuration-framework-a-prioritized-guide-to-hardening-windows-10/

so, My questions :

  1. Do implementing the security hardening using the Windows Servutiy Baseline enough without checking the L1 Enterprise Basic Security documented here?

  2. What are the main differences in security control implemented by the two approaches, are they the same or different! if different, how can you know the difference in mean of controls between the two approaches?

Thanks

Modern Standby

Can you please add some context as to how Modern Standby relates to a secure configuration?

Still active?

Hello

Is this framework still relevant? if not what have taken its place.
Level 4 and 5 is missing.

Deploy Windows Quality Updates within 4 days

Hello,
My input here would be to state that the deployment should be prepared and started within 4 days, and completed within the shortest possible time frame, however i doubt any 'enterprise' does this within 4 days.
When looking at most mid to large size enterprises they usually follow a process where updates are deployed in stages, such as Test, Pilot and the into production. What i usually recommend and also see happening is

  1. Patch/Update is released, start immediate deployment to test ring (2-3 days)
  2. Deploy to pilot ring (2-4 days)
  3. Deploy into production (3-5 days)

This comes close to patching is completed 2.5 weeks after its release.
Any thoughts?

Level 1 with non Domain Joined Devices

Hi,

I have around 15 windows 10 machine and they are nondomain joined, they are used for the daily working process and accessing cloud data, mainly the used programs are web browsers and office applications with some default windows applications.

I went over the Level 1 security recommendation pointed here: https://github.com/microsoft/SecCon-Framework/blob/master/level-1-enterprise-basic-security.md and thinking to skip the security recommendations that have the Domain member as my devices are not domain-joined.

is that a correct approach to implement the previously mentioned recommendation ! to skip Domain member controles on the non-domain devices?

Thanks in advance.

Gap Analysis

is there a simple way to map the requirements of a Level 1 Enterprise Basic Security configuration against an existing domain joined w10-endpoint?

I found the security baselines within the Security Compliance Toolkit but they don't seem to be the same as the Level 1-5 configurations?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.