NIST SP 800-53 Rev. 5 SC-18(2) — Acquisition, Development, And Use

What this control requires

Verify that the acquisition, development, and use of mobile code to be deployed in the system meet the organization's defined mobile code requirements. This ensures that mobile code is secure, compliant, and aligns with organizational policies and standards before it is implemented within the system. This control supports the Code Management, Security Compliance capability within the System and Communications Protection family.

In plain English

Verify that the acquisition, development, and use of mobile code to be deployed in the system meet the organization's defined mobile code requirements. In practice, this means you can prove you policy 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-18(2)) 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.

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Secure Development

Pipeline. Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline.

Branch protection. Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence.

Operational checklist

• Policy. 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.
• System. Document the trigger, the owner and the cadence.
• Control. Document the trigger, the owner and the cadence.
• Scope: management, organization, system, protection, compliance, capability, policy, requirements.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.
• Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Signed policy or standard documents the safeguard. Focus: Acquisition, Development, And Use.

Common pitfalls

• Pilot MDM rollouts that quietly exclude executives or engineers; carving out the highest-risk users is the most common audit failure.
• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.
• CI security checks set to warn-only; the merge button is faster than the security feedback.

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.14.3 — Security Alerts, Advisories, and Directives
• HIPAA (45 CFR Part 164) 164.314(a)(2)(ii) — Other Arrangements
• ISO/IEC 27001:2022 A.8.29 — Security testing in development and acceptance
• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions

Related controls in NIST SP 800-53 Rev. 5

• Control SC-18(1) — Identify Unacceptable Code And Take Corrective Actions
• Control SC-23(3) — Unique System-Generated Session Identifiers
• Control SC-31(3) — Measure Bandwidth In Operational Environments
• Control SC-39(2) — Separate Execution Domain Per Thread
• Control SC-15(4) — Explicitly Indicate Current Participants
• Control SC-38 — Operations Security

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control SC-18(2)

Topics: governance riskendpoint protectionpolicy managementsecure development