security requirement

{
  "id": "MLC-T-CYB-003841",
  "term": "security requirement",
  "field": "Cybersecurity",
  "definition": "1. A requirement levied on an information system or an organization that is derived from applicable laws, executive orders, directives, regulations, policies, standards, procedures, or mission/business needs to ensure the confidentiality, integrity, and availability of information that is being processed, stored, or transmitted.\n\n2. A requirement that has security relevance.\n\n3. A requirement levied on a system or an organization that is derived from applicable laws, Executive Orders, directives, regulations, policies, standards, procedures, or mission/business needs to ensure the confidentiality, integrity, and availability of information that is being processed, stored, or transmitted.\n\n4. Requirements levied on an information system that are derived from applicable laws, Executive Orders, directives, policies, standards, instructions, regulations, or procedures, or organizational mission/business case needs to ensure the confidentiality, integrity, and availability of the information being processed, stored, or transmitted.\n\n5. Requirements levied on an information system that are derived from applicable laws, Executive Orders, directives, policies, standards, instructions, regulations, procedures, or organizational mission/business case needs to ensure the confidentiality, integrity, and availability of the information being processed, stored, or transmitted.\n\n6. A requirement levied on an information system or an organization that is derived from applicable laws, Executive Orders, directives, policies, standards, instructions, regulations, procedures, and/or mission/business needs to ensure the confidentiality, integrity, and availability of information that is being processed, stored, or transmitted.\nNote: Security requirements can be used in a variety of contexts from high-level policy-related activities to low-level implementation-related activities in system development and engineering disciplines.\n\n7. A requirement that specifies the functional, assurance, and strength characteristics for a mechanism, system, or system element.\n\n8. A requirement levied on an information system or an organization that is derived from applicable laws, executive orders, directives, policies, standards, instructions, regulations, procedures, and/or mission/business needs to ensure the confidentiality, integrity, and availability of information that is being processed, stored, or transmitted. Note: Security requirements can be used in a variety of contects from high-level policy activies to low-level implementation activities in system development and engineering disciplines.\n\n9. Requirements levied on an information system that are derived from laws, executive orders, directives, policies, instructions, regulations, or organizational (mission) needs to ensure the confidentiality, integrity, and availability of the information being processed, stored, or transmitted.",
  "references": [
    "NIST SP 800-53A Rev. 5 from FIPS 200 (Adapted); NIST SP 800-53 Rev. 5 from FIPS 200 (Adapted); NIST SP 800-53B from FIPS 200 (Adapted)",
    "NIST SP 800-160v1r1",
    "NIST SP 800-171r3 from FIPS 200 (adapted), NIST SP 800-53 Rev. 5 (adapted)",
    "FIPS 200; CNSSI 4009-2015 from FIPS 200",
    "NIST SP 800-137 from FIPS 200; NIST SP 800-30 Rev. 1 from FIPS 200; NIST SP 800-37 Rev. 1 [Superseded] from FIPS 200; NIST SP 800-39 from FIPS 200; NIST SP 800-53A Rev. 4 [Superseded] from FIPS 200",
    "NIST SP 800-53 Rev. 4 [Superseded] from FIPS 200 (Adapted)",
    "NIST SP 800-160 Vol. 2 [Superseded] from NIST SP 800-160 Vol. 1; NIST SP 800-160 Vol. 1; NIST SP 800-160 Vol. 2 Rev. 1 from NIST SP 800-160 Vol. 1",
    "NIST SP 800-37 Rev. 2 from FIPS 200 (adapted)",
    "NIST SP 800-18 Rev. 1 [Superseded]",
    "NIST CSRC Glossary"
  ],
  "url": "https://mlchart.com/terminology/cybersecurity/security-requirement/"
}