BaselineWatch
7 requirements
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

NIST platform security: roots of trust, firmware and secure enclaves SP 800-219

7 requirements · published 2022-06-24
Changes in this version
All1 Introduction2 Project Description
RefTitleText
1 Introduction The National Institute of Standards and Technology (NIST) has traditionally published secure configuration guides for Apple desktop/laptop operating system versions as prose-based Special Publications (SPs), such as NIST SP 800-179, Revisio
1.1
in 1
 Purpose and Scope The purpose of this document is to introduce the mSCP to broader audiences. This document provides a high-level overview of the mSCP, its components, and some common use cases. It refers readers to the online project documentation for in-de
1.2
in 1
 Audience This document and the mSCP GitHub site are intended for system administrators, security professionals, policy authors, privacy officers, and auditors who have responsibilities involving macOS security. Additionally, vendors of device manage
1.3
in 1
 Relevance to NIST SP 800-70 and the National Checklist Program The security baselines from the mSCP GitHub page are included in the National Checklist Program. As NIST SP 800-70, Revision 4 [4] explains, federal agencies are required to use appropriate security configuration checklists from the Nationa
1.4
in 1
 Document Structure The remaining sections and appendices of this document are as follows: • Section 2 provides an overview of the project, including what its goals are and how its content can be used. • Section 3 explains the major components of the mSCP and
2 Project Description The mSCP is an open-source project that provides a programmatic approach to generating and using macOS security configuration baselines. The project’s content can be used to create customized security baselines of technical security control
2.1
in 2
 Project Goals Apple releases a new macOS version every year, and generally, agencies and organizations must wait for guidance or accept risk before deploying the new macOS version. Most agencies or organizations must create their own internal security co

7 of 7.