U.S. flag   An official website of the United States government
Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock (Dot gov) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

A  |  B  |  C  |  D  |  E  |  F  |  G  |  H  |  I  |  J  |  K  |  L  |  M  |  N  |  O  |  P  |  Q  |  R  |  S  |  T  |  U  |  V  |  W  |  X  |  Y  |  Z

security requirement

Definition(s):

  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.
Source(s):
FIPS 200 under SECURITY REQUIREMENTS
CNSSI 4009-2015 under security requirements from FIPS 200

  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.
Source(s):
NIST SP 800-137 under Security Requirements from FIPS 200
NIST SP 800-30 Rev. 1 under Security Requirements from FIPS 200
NIST SP 800-39 under Security Requirements from FIPS 200
NIST SP 800-53A Rev. 4 under Security Requirements from FIPS 200
NIST SP 800-37 Rev. 1 [Superseded] under Security Requirements from FIPS 200

  A requirement that specifies the functional, assurance, and strength characteristics for a mechanism, system, or system element.
Source(s):
NIST SP 800-160 Vol. 1
NIST SP 800-160 Vol. 2 from NIST SP 800-160 Vol. 1

  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.
Source(s):
NIST SP 800-37 Rev. 2

  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.
Source(s):
NIST SP 800-18 Rev. 1 under Security Requirements

  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. Note: 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.
Source(s):
NIST SP 800-53 Rev. 5 from FIPS 200 - Adapted
NIST SP 800-53B from FIPS 200 - Adapted

  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 contexts from high-level policy-related activities to low-level implementation-related activities in system development and engineering disciplines.
Source(s):
NIST SP 800-53 Rev. 4 [Superseded] under Security Requirement from FIPS 200 - Adapted

  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 contexts from high-level policy-related activities to low-level implementation-related activities in system development and engineering disciplines.
Source(s):
NIST SP 800-53 Rev. 4 [Superseded] under Security Requirement from FIPS 200 - Adapted