# NIST SP 800-53 Rev. 5 PL-11 — Baseline Tailoring - Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pl-11-baseline-tailoring - 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) › PL — Planning - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **NIST SP 800-53 Rev. 5**·Control `PL-11`·high·Component: **Planning** ## What this control requires > Tailor the selected control baseline by applying specified actions to customize it according to the organization's mission, business functions, operating environment, threats, and vulnerabilities. Tailoring actions involve designating common controls, applying scoping considerations, selecting compensating controls, and supplementing the baseline with additional controls as necessary. This control supports the Control Tailoring Process capability within the Planning family. > > — NIST SP 800-53 Rev. 5, Control PL-11 ### In plain English Tailor the selected control baseline by applying specified actions to customize it according to the organization's mission, business functions, operating environment, threats, and vulnerabilities. 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 **Planning**, the assessor will trace your implementation back to the catalogue reference (Control PL-11) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Configuration Management **Policy-as-code.** Codify the control as Service Control Policies (AWS), Azure Policy initiatives, or Organisation Policy (GCP) so the platform enforces what the document promises. **IaC.** Gate Terraform / Pulumi / CloudFormation changes with Checkov / tfsec / OPA so misconfigurations never reach production. **Drift.** Run a CSPM (Wiz / Prisma / Defender for Cloud / Security Command Center) over every account and route findings to a single risk register. #### 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. #### 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. ### Operational checklist - **Policy.** Document the trigger, the owner and the cadence. - **Process.** Document the trigger, the owner and the cadence. - **Configuration.** Document the trigger, the owner and the cadence. - **Additional.** Document the trigger, the owner and the cadence. - **Control.** Document the trigger, the owner and the cadence. - **Scope:** management, actions, mission, organization, functions, controls, configuration, mission business functions. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Baseline Tailoring. ## Common pitfalls - Manual cloud-console changes that never make it back to Terraform — drift accumulates until the next outage forces a reconciliation. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. - Scans that hit only the perimeter; missing authenticated scans of OS, runtime libs and base images so most CVEs are invisible. ## 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. - [**BSI C5:2020 OPS-23** — Managing Vulnerabilities, Malfunctions and Errors - System Hardening](https://support.icompaas.com/compliance/bsi-c5-2020/ops-23-managing-vulnerabilities-malfunctions-and-errors-system-hardening) ## Related controls in NIST SP 800-53 Rev. 5 - [**Control SA-11(5)** — Penetration Testing](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-11-5-penetration-testing) - [**Control PM-32** — Purposing](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pm-32-purposing) - [**Control CP-7** — Alternate Processing Site](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-7-alternate-processing-site) - [**Control SA-4(8)** — Continuous Monitoring Plan For Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/sa-4-8-continuous-monitoring-plan-for-controls) - [**Control CP-2(4)** — Resume All Mission And Business Functions](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/cp-2-4-resume-all-mission-and-business-functions) - [**Control PL-9** — Central Management](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/pl-9-central-management) ## 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 PL-11` Topics: governance riskconfiguration managementpolicy managementvulnerability 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.