# NIST SP 800-53 Rev. 5 SC-43 — Usage Restrictions - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-43-usage-restrictions - Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › SC — System and Communications Protection - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `SC-43`·high·Component: **System and Communications Protection** ## What this control requires > Establish and enforce usage restrictions and implementation guidelines for specified system components, including mobile code, devices, and peripherals like printers and scanners. These guidelines help prevent unauthorized use and reduce the risk of damage to the system. Regular monitoring and control of component usage ensure that only authorized personnel access and operate these components. This control supports the System components, access management capability within the System and Communications Protection family. > > — NIST SP 800-53 Rev. 5, Control SC-43 ### In plain English Establish and enforce usage restrictions and implementation guidelines for specified system components, including mobile code, devices, and peripherals like printers and scanners. In practice, this means you can prove you restrictions management-level controls on a defined cadence. ## Why it matters SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed. This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation. ## What an auditor looks for A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan. Within **System and Communications Protection**, the assessor will trace your implementation back to the catalogue reference (Control SC-43) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Endpoint Protection **MDM.** Make MDM enrollment a hard gate for device access (Intune compliance + Conditional Access, or Jamf + Okta device trust). Unmanaged devices simply don't get a session token. **EDR.** Deploy CrowdStrike / SentinelOne / Defender for Endpoint to every server and laptop; alert on any host that stops sending telemetry for >24h. ### Operational checklist - **Restrictions.** Document the trigger, the owner and the cadence. - **Usage.** Document the trigger, the owner and the cadence. - **Access.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Protection.** Document the trigger, the owner and the cadence. - **Scope:** management, system, only, personnel, protection, usage restrictions, components, capability. ## Evidence to collect - **User Device Scan.** MDM compliance state per user device (Intune / Jamf / Workspace ONE). Endpoint compliance telemetry (Intune, Jamf) proves managed coverage. Focus: Usage Restrictions. ## Common pitfalls - Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**NIST SP 800-171 Rev. 3 3.1.18** — Access Control for Mobile Devices](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-1-18-access-control-for-mobile-devices) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control AC-17(1)** — Monitoring And Control](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ac-17-1-monitoring-and-control) - [**Control PE-10** — Emergency Shutoff](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-10-emergency-shutoff) - [**Control SC-34(1)** — No Writable Storage](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-34-1-no-writable-storage) - [**Control SC-18(5)** — Allow Execution Only In Confined Environments](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-18-5-allow-execution-only-in-confined-environments) - [**Control SR-4(3)** — Validate As Genuine And Not Altered](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-4-3-validate-as-genuine-and-not-altered) - [**Control SC-15** — Collaborative Computing Devices And Applications](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-15-collaborative-computing-devices-and-applications) ## References - [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls) - Catalogue identifier: `Control SC-43` Topics: governance riskendpoint securitylogging monitoringendpoint protectioncontinuous monitoring ## Related compliance guidance - [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs. - [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement. - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.