macos_security
CIS-for-macOS-BigSur-Intel-M1
| macos_security | CIS-for-macOS-BigSur-Intel-M1 | |
|---|---|---|
| 18 | 1 | |
| 1,565 | 6 | |
| 2.5% | - | |
| 9.1 | 0.0 | |
| 1 day ago | almost 3 years ago | |
| YAML | ||
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
macos_security
- Windows Security Compliance project
-
FIPS 140 and MacOS
For starters there's an entire NIST project for macOS Security Compliance - https://github.com/usnistgov/macos_security this will make your life a million times easier to meet a lot of the technical controls required for compliance. Nothing like this really exists for Windows or Linux(closest is Compliance As Code https://github.com/ComplianceAsCode/content)
-
Nist controls and acceptable artifacts and evidence. Does anyone have a controls spreadsheet that lists all 800-53 controls and evidence required to satisfy that control?
https://github.com/usnistgov/macos_security - for macOS this would help.
-
Need reporting about device CIS compliance
I’d highly recommend checking out the usnistgov/macos_security on GitHub. You can generate a benchmark and then feed the output into extension attributes to trigger policies on.
- CIS Benchmark deployment approach
-
Could use some advice on my career change
Study about cybersecurity, or how to harden a macOS fleet against published security frameworks.
-
Enrolling devices in ABM/Mosyle
Weigh the pros and cons about having your end-users be standard users or admins on their Macs. If they are already admins (probably), consider the political blowback if you take away their admin rights and flexibility and autonomy they've become used to. Conversely, consider the security posture of your organization. If it has to adhere to some well-known guides (like 800-171 o 800-53r5), then you may not be able to allow end-users to be admins. Take a look at the macOS Security Compliance Project.
-
Here's a recap of the top-voted webinar: How to Harden Macs!
NIST Compliance Benchmarks: github.com/usnistgov/macos_security
- Hardening macOS
-
Disabling Bonjour on monterey
Like OP, I'm trying to disable both bonjour and netbios. I'm using this script: https://github.com/usnistgov/macos_security/blob/main/includes/enablePF-mscp.sh
CIS-for-macOS-BigSur-Intel-M1
-
CIS Benchmarks
I am during implementation of cis for one of my customers. I did as it said here: https://github.com/colorenz/CIS-for-macOS-BigSur-Intel-M1
What are some alternatives?
macOS-Security-and-Privacy-Guide - Guide to securing and improving privacy on macOS
Installomator - Installation script to deploy standard software on Macs
CIS-macOS-Security
heimdall2 - Heimdall Enterprise Server 2 lets you view, store, and compare automated security control scan results.
windows_hardening - HardeningKitty and Windows Hardening settings and configurations
TheMacHardeningScripts - Scripts to secure and harden Mac OS X
CIS-for-macOS-Catalina-CP - CIS Benchmarks for macOS Catalina
santa - A binary authorization and monitoring system for macOS
saf - The MITRE Security Automation Framework (SAF) Command Line Interface (CLI) brings together applications, techniques, libraries, and tools developed by MITRE and the security community to streamline security automation for systems and DevOps pipelines
scriptsandthings_Jamf_JSON_Schemas - JSON Schemas for Jamf Pro - For configuration of application settings from within the Jamf web GUI
content - Security automation content in SCAP, Bash, Ansible, and other formats