Term:Configuration Control

From FISMApedia
Revision as of 00:39, 27 October 2009 by DanPhilpott (talk) (1 revision)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

CNSSI 4009

Configuration Control - Process of controlling modifications to hardware, firmware, software, and documentation to ensure the IS is protected against improper modifications prior to, during, and after system implementation.

DSS Glossary

Configuration Control - Process of controlling modifications to hardware, firmware, software, and documentation to ensure the information system is protected against improper modifications prior to, during, and after system implementation.

GAO-09-232G

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to ensure the information system is protected against improper modifications prior to, during, and after system implementation.

NIST IR 7298

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to ensure the information system is protected against improper modifications prior to, during, and after system implementation. SOURCE: SP 800-53; CNSSI-4009

NIST IR 7328 Draft

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to protect the information system against improper modifications before, during, and after system implementation. [CNSS Inst. 4009]

NIST SP 800-18r1

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to ensure that the information system is protected against improper modifications before, during, and after system implementation. [CNSS Inst. 4009]

NIST SP 800-37r1 Draft

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to protect the information system against improper modifications before, during, and after system implementation. [CNSS Inst. 4009]

NIST SP 800-37

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to ensure the information system is protected against improper modifications prior to, during, and after system implementation. [CNSS Inst. 4009]

NIST SP 800-39 Draft 2

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to protect the information system against improper modifications before, during, and after system implementation. [CNSS Inst. 4009]

NIST SP 800-53A

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to protect the information system against improper modifications before, during, and after system implementation. [CNSS Inst. 4009]

NIST SP 800-53r1

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to protect the information system against improper modifications before, during, and after system implementation.

NIST SP 800-53r2

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to protect the information system against improper modifications before, during, and after system implementation. [CNSS Inst. 4009]

NIST SP 800-53r3

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to protect the information system against improper modifications before, during, and after system implementation. [CNSSI 4009]

NIST SP 800-82 Final Draft

Configuration Control - Process for controlling modifications to hardware, firmware, software, and documentation to ensure the information system is protected against improper modifications before, during, and after system implementation.[National Information Assurance (IA) Glossary, CNSS Instruction no. 4009, revised June 2006.]

NSTISSI 1000

Configuration Control - Process of controlling modifications to hardware, firmware, software, and documentation to ensure the IS is protected against improper modifications prior to, during, and after system implementation.