# PL-07 Concept of Operations

NIST SP 800-53 control. Family: PL Planning. Function: preventative. In no baseline. Mapping licence: CC BY-SA 4.0.

Statement: a. Develop a Concept of Operations (CONOPS) for the system describing how the organization intends to operate the system from the perspective of information security and privacy; and b. Review and update the CONOPS [Assignment: organization-defined frequency].
Guidance: The CONOPS may be included in the security or privacy plans for the system or in other system development life cycle documents. The CONOPS is a living document that requires updating throughout the system development life cycle. For example, during system design reviews, the concept of operations is checked to ensure that it remains consistent with the design for controls, the system architecture, and the operational procedures. Changes to the CONOPS are reflected in ongoing updates to the security and privacy plans, security and privacy architectures, and other organizational documents, such as procurement specifications, system development life cycle documents, and systems engineering documents.

## Clauses by framework (18 frameworks)
- iso_27001_2022: 8.1, A.5.8
- cobit_2019: BAI02
- rbi_csf: ITGRCA.4
- hkma_tme1: TME1.2.2, TME1.3.1
- mlps_2: 8.1.9.2
- cra: CRA.Info.4
- cbb_tm: TM-2
- bog_cisd: CISD-I
- bot_cyber: Ch6.2
- eba_ict: 3.6.1
- ffiec_is: II.C.1
- nydfs_500: 500.2
- common_criteria: CC Part 1 — PP
- fda_cyber: SPDF-3
- hitrust_csf: 10.a
- naic_ds: 4
- csa_ccm_v4: BCR-05
- csa_aicm: BCR-05
OSA's mapping for iso_27001_2022 takes NIST's published crosswalk as its base. A clause not marked as OSA's own is in that crosswalk.

## More
- This control as JSON, with guidance and ATT&CK techniques: /api/v1/controls/PL-07
- Clauses only: /api/v1/controls/PL-07?fields=mappings
- Page for people: /controls/pl-07/
- Found an error? Open an issue at https://github.com/opensecurityarchitecture/osa-data/issues with the id, what OSA says and what the source says.