IAO-04.1: Plan / Coordinate with Other Organizational Entities
Mechanisms exist to plan and coordinate Control Validation Testing (CVT) activities with affected stakeholders before conducting such activities in order to reduce the potential impact on operations.
Renumbered: Formerly IAO-03.1 in SCF 2025.4.
Control Question: Does the organization plan and coordinate Information Assurance Program (IAP) activities with affected stakeholders before conducting such activities in order to reduce the potential impact on operations?
General (22)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC4.1 |
| GovRAMP | PL-02 |
| GovRAMP Low | PL-02 |
| GovRAMP Low+ | PL-02 |
| GovRAMP Moderate | PL-02 |
| GovRAMP High | PL-02 |
| NIST 800-37 R2 | TASK P-9 |
| NIST 800-53 R4 | PL-2(3) |
| NIST 800-53 R5.2 | PL-02 |
| NIST 800-53B R5 (low) (source) | PL-02 |
| NIST 800-53B R5 (moderate) (source) | PL-02 |
| NIST 800-53B R5 (high) (source) | PL-02 |
| NIST 800-53B R5 (privacy) (source) | PL-02 |
| NIST 800-82 R3 | PL-02 |
| NIST 800-82 R3 LOW OT Overlay | PL-02 |
| NIST 800-82 R3 MODERATE OT Overlay | PL-02 |
| NIST 800-82 R3 HIGH OT Overlay | PL-02 |
| NIST 800-161 R1 | PL-2 |
| NIST 800-161 R1 C-SCRM Baseline | PL-2 |
| NIST 800-161 R1 Flow Down | PL-2 |
| NIST 800-161 R1 Level 3 | PL-2 |
| NIST 800-171 R2 (source) | NFO - PL-2(3) |
US (11)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | PL-2 PL-2(3) |
| USA Federal CJIS Security Policy 6.0 | PL-2 |
| USA Federal FFIEC ITEH 2016 | IV.A.1 |
| USA Federal FedRAMP R5 (low) | PL-02 |
| USA Federal FedRAMP R5 (moderate) | PL-02 |
| USA Federal FedRAMP R5 (high) | PL-02 |
| USA Federal FedRAMP R5 (LI-SaaS) | PL-02 |
| USA Federal IRS 1075 2021 | PL-2 |
| USA Texas DIR SCSC 2.2 2025 | PL-02 |
| USA Texas TX-RAMP Level 1 | PL-02 |
| USA Texas TX-RAMP Level 2 | PL-02 |
Capability Maturity Model
Level 0 — Not Performed
Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.
Level 1 — Performed Informally
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Information Assurance (IAO) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IAO domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with IAO domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IAO domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Information Assurance (IA)-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ IA management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ Pre-production security testing is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ IT and/or cybersecurity personnel implement and maintain a limited Information Assurance Program (IAP) capability to conduct limited control testing to meet specific statutory, regulatory and/or contractual requirements for pre-production cybersecurity and data protection control testing.
Level 3 — Well Defined
Information Assurance (IAO) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with IAO domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with IAO domain capabilities are well-documented and kept current by process owners. ▪ An information assurance team, or similar function, is appropriately staffed and supported to implement and maintain IAO domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of information assurance operations (e.g., assessment scheduling software and risk assessment software). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with IAO domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to plan and coordinate Information Assurance Program (IAP) activities with affected stakeholders before conducting such activities in order to reduce the potential impact on operations.
Level 4 — Quantitatively Controlled
Information Assurance (IAO) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.
Level 5 — Continuously Improving
Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.
Assessment Objectives
- IAO-04.1_A01 a cybersecurity / data privacy plan for the system is developed that describes the operational environment for the system and any dependencies on or connections to other systems or system components.
- IAO-04.1_A02 stakeholders whose operations may be affected by Control Validation Testing (CVT) activities are identified.
- IAO-04.1_A03 Control Validation Testing (CVT) activities are planned and coordinated with affected stakeholders before the activities are conducted.
Evidence Requirements
- E-IAO-04 Security Assessment Plan
-
Documented evidence of a plan to conduct security assessments.
Information Assurance
Technology Recommendations
Micro/Small
- Notify affected staff before security testing
Small
- Testing schedule communicated to affected teams
Medium
- Assessment planning with stakeholder coordination (change calendar, notifications)
Large
- Formal assessment planning and coordination with business units, IT operations and third parties
- Audit steering committee
Enterprise
- Enterprise assurance planning integrated with change management and operations calendars
- Audit steering committee governance