Closed Security Environment

From FISMApedia
Jump to: navigation, search

CNSSI 4009

Environment providing sufficient assurance that applications and equipment are protected against the introduction of malicious logic during an IS life cycle. Closed security is based upon a system's developers, operators, and maintenance personnel having sufficient clearances, authorization, and configuration control.
{"cc_re__cc_re__cc_by_sa_4_0": ["a href=\"/index.php/FISMApedia:Privacy_policy\" title=\"FISMApedia:Privacy policy\">Privacy policy</a></li>\n\t\t\t\t\t\t\t\t\t\t\t<li id=\"footer-places-about\"><a href=\"/index.php/FISMApedia:About\" title=\"FISMApedia:About\">About FISMApedia</a></li>\n\t\t\t\t\t\t\t\t\t\t\t<li id=\"footer-places-disclaimer\"><a href=\"/index.php/FISMApedia:General_disclaimer\" title=\"FISMApedia:General disclaimer\">Disclaimers</a></li>\n\t\t\t\t\t\t\t\t\t</ul>\n\t\t\t\t\t\t\t\t\t\t<ul id=\"footer-icons\" class=\"noprint\">\n\t\t\t\t\t\t\t\t\t\t\t<li id=\"footer-copyrightico\">\n\t\t\t\t\t\t\t<a href=\"https://creativecommons.org/licenses/by-sa/4.0/\"><img src=\"/resources/assets/licenses/cc-by-sa.png\" alt=\"Creative Commons Attribution-ShareAlike\" width=\"88\" height=\"31\"/></a>\t\t\t\t\t\t</li>\n\t\t\t\t\t\t\t\t\t\t\t<li id=\"footer-poweredbyico\">\n\t\t\t\t\t\t\t<a href=\"//www.mediawiki.org/\"><img src=\"/resources/assets/poweredby_mediawiki_88x31.png\" alt=\"Powered by MediaWiki\" srcset=\"/resources/assets/poweredby_mediawiki_132x47.png 1.5x, /resources/assets/poweredby_mediawiki_176x62.png 2x\" width=\"88\" height=\"31\"/></a>\t\t\t\t\t\t</li>\n\t\t\t\t\t\t\t\t\t</ul>\n\t\t\t\t\t\t<div style=\"clear:bot"], "copyright__copyright__copyright": ["Closed Security Environment\n\nFrom FISMApedia\nJump to: navigation, search\n\nCNSSI 4009\n\nEnvironment providing sufficient assurance that applications and equipment are protected against the introduction of malicious logic during an IS life cycle. Closed security is based upon a system's developers, operators, and maintenance personnel having sufficient clearances, authorization, and configuration control.", "Closed Security Environment\n\nFrom FISMApedia\nJump to: navigation, search\n\nCNSSI 4009\n\nEnvironment providing sufficient assurance that applications and equipment are protected against the introduction of malicious logic during an IS life cycle. Closed security is based upon a system's developers, operators, and maintenance personnel having sufficient clearances, authorization, and configuration control.", "Closed Security Environment\n\nFrom FISMApedia\nJump to: navigation, search\n\nCNSSI 4009\n\nEnvironment providing sufficient assurance that applications and equipment are protected against the introduction of malicious logic during an IS life cycle. Closed security is based upon a system's developers, operators, and maintenance personnel having sufficient clearances, authorization, and configuration control.", "Closed Security Environment\n\nFrom FISMApedia\nJump to: navigation, search\n\nCNSSI 4009\n\nEnvironment providing sufficient assurance that applications and equipment are protected against the introduction of malicious logic during an IS life cycle. Closed security is based upon a system's developers, operators, and maintenance personnel having sufficient clearances, authorization, and configuration control.", "Closed Security Environment\n\nFrom FISMApedia\nJump to: navigation, search\n\nCNSSI 4009\n\nEnvironment providing sufficient assurance that applications and equipment are protected against the introduction of malicious logic during an IS life cycle. Closed security is based upon a system's developers, operators, and maintenance personnel having sufficient clearances, authorization, and configuration control."]}