Mechanisms exist to require system developers and integrators to perform configuration management during system design, development, implementation and operation.
Mechanisms exist to require developer of systems, system components or services to enable integrity verification of software and firmware components.
Mechanisms exist to require developer of systems, system components or services to enable integrity verification of hardware components.
Mechanisms exist to require system developers and integrators to create a Security Test and Evaluation (ST&E) plan and implement the plan under the witness of an independent party.
Mechanisms exist to require the developers of systems, system components or services to provide training on the correct use and operation of the system, system component or service.
Mechanisms exist to prevent unsupported systems by: â–ª Replacing systems when support for the components is no longer available from the developer, vendor or manufacturer; and â–ª Requiring justification and documented approval for the continued use of unsupported system components required to satisfy mission/business needs.
Mechanisms exist to provide in-house support or contract external providers for support with unsupported system components.
Mechanisms exist to check the validity of information inputs.
Mechanisms exist to handle error conditions by: â–ª Identifying potentially security-relevant error conditions; â–ª Generating error messages that provide information necessary for corrective actions without revealing sensitive or potentially harmful information in error logs and administrative messages that could be exploited; and â–ª Revealing error messages only to authorized personnel.
Mechanisms exist to limit privileges to change software resident within software libraries.
Passcode