# NIST SP 800-53 Rev. 5 SR-11(3) — Anti-Counterfeit Scanning - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-11-3-anti-counterfeit-scanning - 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) › SR — Supply Chain Risk Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `SR-11(3)`·medium·Component: **Supply Chain Risk Management** ## What this control requires > Scan for counterfeit system components at an organization-defined frequency. The type of component determines the type of scanning to be conducted (e.g., web application scanning for web application components). This control supports the Security and Compliance capability within the Supply Chain Risk Management family. > > — NIST SP 800-53 Rev. 5, Control SR-11(3) ### In plain English Scan for counterfeit system components at an organization-defined frequency. 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. ## 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 **Supply Chain Risk Management**, the assessor will trace your implementation back to the catalogue reference (Control SR-11(3)) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Vulnerability Management **Scanners.** Pair an unauthenticated scanner (Nessus / Qualys / Tenable.io) for external surface with an authenticated agent for OS/library CVEs on every host. **SLA.** Document remediation SLAs by CVSS / EPSS: critical 7 days, high 30 days, medium 90 days; report monthly trend to leadership. **Containers.** Scan images in CI (Trivy / Grype / Snyk Container) AND at runtime; block deploys on critical findings without exception. #### 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. ### Operational checklist - **Policy.** Document the trigger, the owner and the cadence. - **Security.** Document the trigger, the owner and the cadence. - **Chain.** 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, application, e, web, compliance, components. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Anti-Counterfeit Scanning. ## Common pitfalls - Scans that hit only the perimeter; missing authenticated scans of OS, runtime libs and base images so most CVEs are invisible. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## 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. - [**HIPAA (45 CFR Part 164) 164.308(a)(5)(i)** — Security Awareness and Training](https://support.icompaas.com/compliance/hipaa/164-308-a-5-i-security-awareness-and-training) - [**NIST SP 800-171 Rev. 3 3.4.11** — Information Location](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-4-11-information-location) - [**BSI C5:2020 SP-01** — Documentation, communication and provision of policies and instructions](https://support.icompaas.com/compliance/bsi-c5-2020/sp-01-documentation-communication-and-provision-of-policies-and-instructions) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SA-19(4)** — Anti-Counterfeit Scanning](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-19-4-anti-counterfeit-scanning) - [**Control SR-10** — Inspection Of Systems Or Components](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-10-inspection-of-systems-or-components) - [**Control SR-12** — Component Disposal](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sr-12-component-disposal) - [**Control SC-29** — Heterogeneity](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sc-29-heterogeneity) - [**Control SA-22(1)** — Alternative Sources For Continued Support](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-22-1-alternative-sources-for-continued-support) - [**Control PE-13(4)** — Inspections](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pe-13-4-inspections) ## 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 SR-11(3)` Topics: governance riskvulnerability managementpolicy management ## 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.