All Projects → usnistgov → Macos_security

usnistgov / Macos_security

Licence: other
macOS Security Compliance Project

Programming Languages

python3
1442 projects
bash
514 projects

Projects that are alternatives of or similar to Macos security

Dockerized lara
Build your Laravel App with Redis - Mongodb - MariaDB - Nginx - php7 - zsh
Stars: ✭ 9 (-97.41%)
Mutual labels:  zsh, yaml
Jaromail
A commandline tool to easily and privately handle your e-mail
Stars: ✭ 86 (-75.29%)
Mutual labels:  zsh, apple
Zsh Apple Touchbar
Make your touchbar more powerful.
Stars: ✭ 261 (-25%)
Mutual labels:  zsh, apple
Jk
Configuration as Code with ECMAScript
Stars: ✭ 322 (-7.47%)
Mutual labels:  yaml
Zsh Autosuggestions
Fish-like autosuggestions for zsh
Stars: ✭ 19,697 (+5560.06%)
Mutual labels:  zsh
Webbrowser
iOS浏览器 Web Browser for iOS
Stars: ✭ 332 (-4.6%)
Mutual labels:  apple
Cloud Custodian
Rules engine for cloud security, cost optimization, and governance, DSL in yaml for policies to query, filter, and take actions on resources
Stars: ✭ 3,926 (+1028.16%)
Mutual labels:  compliance
Open Source Xamarin Apps
📱 Collaborative List of Open Source Xamarin Apps
Stars: ✭ 318 (-8.62%)
Mutual labels:  apple
Zsh Kubectl Prompt
Display information about the kubectl current context and namespace in zsh prompt.
Stars: ✭ 342 (-1.72%)
Mutual labels:  zsh
Dotbare
Manage dotfiles and any git directories interactively with fzf
Stars: ✭ 327 (-6.03%)
Mutual labels:  zsh
Awsweeper
A tool for cleaning your AWS account
Stars: ✭ 331 (-4.89%)
Mutual labels:  yaml
Macos Security And Privacy Guide
Guide to securing and improving privacy on macOS
Stars: ✭ 18,685 (+5269.25%)
Mutual labels:  apple
Ossec Hids
OSSEC is an Open Source Host-based Intrusion Detection System that performs log analysis, file integrity checking, policy monitoring, rootkit detection, real-time alerting and active response.
Stars: ✭ 3,580 (+928.74%)
Mutual labels:  compliance
Onnx Coreml
ONNX to Core ML Converter
Stars: ✭ 326 (-6.32%)
Mutual labels:  apple
Zsh Better Npm Completion
Better completion for npm
Stars: ✭ 346 (-0.57%)
Mutual labels:  zsh
Hoplite
A boilerplate-free library for loading configuration files as data classes in Kotlin
Stars: ✭ 322 (-7.47%)
Mutual labels:  yaml
Iphonemocapios
Stars: ✭ 338 (-2.87%)
Mutual labels:  apple
Esp32 Homekit
ESP-32 implementation of Apple Homekit Accessory Protocol(HAP)
Stars: ✭ 331 (-4.89%)
Mutual labels:  apple
Nord Dircolors
An arctic, north-bluish clean and elegant dircolors theme.
Stars: ✭ 328 (-5.75%)
Mutual labels:  zsh
Awesome Swift Playgrounds
A List of Awesome Swift Playgrounds
Stars: ✭ 3,521 (+911.78%)
Mutual labels:  apple

image::templates/images/mscp_banner_outline.png[] // settings: :idprefix: :idseparator: - ifndef::env-github[:icons: font] ifdef::env-github[] :status: //:outfilesuffix: .adoc :caution-caption: 🔥 :important-caption: ❗️ :note-caption: 📎 :tip-caption: 💡 :warning-caption: ⚠️ endif::[] :uri-org: https://github.com/usnistgov :uri-repo: {uri-org}/macos_security

ifdef::status[] image:https://badgen.net/badge/icon/apple?icon=apple&label[link="https://www.apple.com/"] image:https://badgen.net/badge/icon/11.0?icon=apple&label[link="https://www.apple.com/macos"] endif::[]

The macOS Security Compliance Project is an link:LICENSE.md[open source] effort to provide a programmatic approach to generating security guidance. The configuration settings in this document were derived from National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, Recommended Security Controls for Federal Information Systems and Organizations, Revision 4. This is a joint project of federal operational IT Security staff from the National Institute of Standards and Technology (NIST), National Aeronautics and Space Administration (NASA), Defense Information Systems Agency (DISA), and Los Alamos National Laboratory (LANL).

This project can be used as a resource to easily create customized security baselines of technical security controls by leveraging a library of atomic actions which are mapped to the compliance requirements defined in NIST SP 800-53 (Rev. 4). It can also be used to develop customized guidance to meet the particular cybersecurity needs of any organization.

To learn more about the project, please see the {uri-repo}/wiki[wiki].

If you are interested in supporting the development of the project, refer to the link:CONTRIBUTING.adoc[contributor guidance] for more information.

== Usage

Civilian agencies are to use the National Checklist Program as required by https://csrc.nist.gov/publications/detail/sp/800-70/rev-4/final[NIST 800-70].

[NOTE]

Part 39 of the Federal Acquisition Regulations, section 39.101 paragraph (c) states, “In acquiring information technology, agencies shall include the appropriate information technology security policies and requirements, including use of common security configurations available from the National Institute of Standards and Technology’s website at https://checklists.nist.gov. Agency contracting officers should consult with the requiring official to ensure the appropriate standards are incorporated.”

== Authors

[width="100%",cols="1,1"] |=== |Bob Gendler|National Institute of Standards and Technology |Allen Golbig|National Aeronautics and Space Administration |Dan Brodjieski|Defense Information Systems Agency |Jason Blake|National Institute of Standards and Technology |Blair Heiserman|National Institute of Standards and Technology |Joshua Glemza|National Aeronautics and Space Administration |Elyse Anderson|National Aeronautics and Space Administration |Gary Gapinski|National Aeronautics and Space Administration |===

== Changelog

Refer to the link:CHANGELOG.adoc[CHANGELOG] for a complete list of changes.

== NIST Disclaimer

Any identification of commercial or open-source software in this document is done so purely in order to specify the methodology adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the software identified are necessarily the best available for the purpose.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].