SC-3(4)—Module Coupling And Cohesiveness
>Control Description
Implement security functions as largely independent modules that maximize internal cohesiveness within modules and minimize coupling between modules.
>Supplemental Guidance
The reduction of inter-module interactions helps to constrain security functions and manage complexity. The concepts of coupling and cohesion are important with respect to modularity in software design. Coupling refers to the dependencies that one module has on other modules.
Cohesion refers to the relationship between functions within a module. Best practices in software engineering and systems security engineering rely on layering, minimization, and modular decomposition to reduce and manage complexity. This produces software modules that are highly cohesive and loosely coupled.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What policies govern the implementation of module coupling and cohesiveness?
- •How are system and communications protection requirements defined and maintained?
- •Who is responsible for configuring and maintaining the security controls specified in SC-3(4)?
Technical Implementation:
- •How is module coupling and cohesiveness technically implemented in your environment?
- •What systems, tools, or configurations enforce this protection requirement?
- •How do you ensure that module coupling and cohesiveness remains effective as the system evolves?
Evidence & Documentation:
- •What documentation demonstrates the implementation of SC-3(4)?
- •Can you provide configuration evidence or system diagrams showing this protection control?
- •What logs or monitoring data verify that this control is functioning correctly?
Ask AI
Configure your API key to use AI features.