NET-04.8: Data Type Identifiers

There is no evidence of a capability to utilize data type identifiers to validate data essential for information flow decisions when transferring information between different security domains.

C|P-CMM1 is N/A, since a structured process is required to utilize data type identifiers to validate data essential for information flow decisions when transferring information between different security domains.

C|P-CMM2 is N/A, since a well-defined process is required to utilize data type identifiers to validate data essential for information flow decisions when transferring information between different security domains.

Network Security (NET) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist:

• A Technology Infrastructure team, or similar function, defines centrally-managed network security controls for implementation across the enterprise.
• Secure engineering principles are used to design and implement network security controls (e.g., industry-recognized secure practices) to enforce the concepts of least privilege and least functionality at the network level.
• IT/cybersecurity architects work with the Technology Infrastructure team to implement a “layered defense” network architecture that provides a defense-in-depth approach for redundancy and risk reduction for network-based security controls, including wired and wireless networking.
• Administrative processes and technologies configure boundary devices (e.g., firewalls, routers, etc.) to deny network traffic by default and allow network traffic by exception (e.g., deny all, permit by exception).
• Technologies automate the Access Control Lists (ACLs) and similar rulesets review process to identify security issues and/ or misconfigurations.
• Network segmentation exists to implement separate network addresses (e.g., different subnets) to connect systems in different security domains (e.g., sensitive/regulated data environments).

See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to utilize data type identifiers to validate data essential for information flow decisions when transferring information between different security domains.

See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to utilize data type identifiers to validate data essential for information flow decisions when transferring information between different security domains.