+SI System and Information Integrity
---+SI-01 Policy and Procedures
---+SI-02 Flaw Remediation
------+SI-02(02) Automated Flaw Remediation Status
------+SI-02(03) Time to Remediate Flaws and Benchmarks for Corrective Actions
------+SI-02(04) Automated Patch Management Tools
------+SI-02(05) Automatic Software and Firmware Updates
------+SI-02(06) Removal of Previous Versions of Software and Firmware
------+SI-02(07) Root Cause Analysis
---+SI-03 Malicious Code Protection
------+SI-03(04) Updates Only by Privileged Users
------+SI-03(06) Testing and Verification
------+SI-03(08) Detect Unauthorized Commands
------+SI-03(10) Malicious Code Analysis
---+SI-04 System Monitoring
------+SI-04(01) System-wide Intrusion Detection System
------+SI-04(02) Automated Tools and Mechanisms for Real-time Analysis
------+SI-04(03) Automated Tool and Mechanism Integration
------+SI-04(04) Inbound and Outbound Communications Traffic
------+SI-04(05) System-generated Alerts
------+SI-04(07) Automated Response to Suspicious Events
------+SI-04(09) Testing of Monitoring Tools and Mechanisms
------+SI-04(10) Visibility of Encrypted Communications
------+SI-04(11) Analyze Communications Traffic Anomalies
------+SI-04(12) Automated Organization-generated Alerts
------+SI-04(13) Analyze Traffic and Event Patterns
------+SI-04(14) Wireless Intrusion Detection
------+SI-04(15) Wireless to Wireline Communications
------+SI-04(16) Correlate Monitoring Information
------+SI-04(17) Integrated Situational Awareness
------+SI-04(18) Analyze Traffic and Covert Exfiltration
------+SI-04(19) Risk for Individuals
------+SI-04(20) Privileged Users
------+SI-04(21) Probationary Periods
------+SI-04(22) Unauthorized Network Services
------+SI-04(23) Host-based Devices
------+SI-04(24) Indicators of Compromise
------+SI-04(25) Optimize Network Traffic Analysis
---+SI-05 Security Alerts, Advisories, and Directives
------+SI-05(01) Automated Alerts and Advisories
---+SI-06 Security and Privacy Function Verification
------+SI-06(02) Automation Support for Distributed Testing
------+SI-06(03) Report Verification Results
---+SI-07 Software, Firmware, and Information Integrity
------+SI-07(01) Integrity Checks
------+SI-07(02) Automated Notifications of Integrity Violations
------+SI-07(03) Centrally Managed Integrity Tools
------+SI-07(05) Automated Response to Integrity Violations
------+SI-07(06) Cryptographic Protection
------+SI-07(07) Integration of Detection and Response
------+SI-07(08) Auditing Capability for Significant Events
------+SI-07(09) Verify Boot Process
------+SI-07(10) Protection of Boot Firmware
------+SI-07(12) Integrity Verification
------+SI-07(15) Code Authentication
------+SI-07(16) Time Limit on Process Execution Without Supervision
------+SI-07(17) Runtime Application Self-protection
---+SI-08 Spam Protection
------+SI-08(02) Automatic Updates
------+SI-08(03) Continuous Learning Capability
---+SI-09 Information Input Restrictions
---+SI-10 Information Input Validation
------+SI-10(01) Manual Override Capability
------+SI-10(02) Review and Resolve Errors
------+SI-10(03) Predictable Behavior
------+SI-10(04) Timing Interactions
------+SI-10(05) Restrict Inputs to Trusted Sources and Approved Formats
------+SI-10(06) Injection Prevention
---+SI-11 Error Handling
---+SI-12 Information Management and Retention
------+SI-12(01) Limit Personally Identifiable Information Elements
------+SI-12(02) Minimize Personally Identifiable Information in Testing, Training, and Research
------+SI-12(03) Information Disposal
---+SI-13 Predictable Failure Prevention
------+SI-13(01) Transferring Component Responsibilities
------+SI-13(03) Manual Transfer Between Components
------+SI-13(04) Standby Component Installation and Notification
------+SI-13(05) Failover Capability
---+SI-14 Non-persistence
------+SI-14(01) Refresh from Trusted Sources
------+SI-14(02) Non-persistent Information
------+SI-14(03) Non-persistent Connectivity
---+SI-15 Information Output Filtering
---+SI-16 Memory Protection
---+SI-17 Fail-safe Procedures
---+SI-18 Personally Identifiable Information Quality Operations
------+SI-18(01) Automation Support
------+SI-18(02) Data Tags
------+SI-18(03) Collection
------+SI-18(04) Individual Requests
------+SI-18(05) Notice of Correction or Deletion
---+SI-19 De-identification
------+SI-19(01) Collection
------+SI-19(02) Archiving
------+SI-19(03) Release
------+SI-19(04) Removal, Masking, Encryption, Hashing, or Replacement of Direct Identifiers
------+SI-19(05) Statistical Disclosure Control
------+SI-19(06) Differential Privacy
------+SI-19(07) Validated Algorithms and Software
------+SI-19(08) Motivated Intruder
---+SI-20 Tainting
---+SI-21 Information Refresh
---+SI-22 Information Diversity
---+SI-23 Information Fragmentation

SI System and Information Integrity

System and Information Integrity

1. Přehled

Název Standard
SI-01 Policy and Procedures

Control

  1. Develop, document, and disseminate to [Assignement: organization-defined personnel or roles]:
    1. [Selection(one-or-more): organization-level; mission/business process-level; system-level] system and information integrity policy that:
      1. Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
      2. Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
    2. Procedures to facilitate the implementation of the system and information integrity policy and the associated system and information integrity controls;
  2. Designate an [Assignement: official] to manage the development, documentation, and dissemination of the system and information integrity policy and procedures; and
  3. Review and update the current system and information integrity:
    1. Policy [Assignement: frequency] and following [Assignement: events] ; and
    2. Procedures [Assignement: frequency] and following [Assignement: events].

Discussion

System and information integrity policy and procedures address the controls in the SI family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of system and information integrity policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to system and information integrity policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.

Assessment Objective

    1. a system and information integrity policy is developed and documented;
    2. the system and information integrity policy is disseminated to [Assignement: personnel or roles];
    3. system and information integrity procedures to facilitate the implementation of the system and information integrity policy and associated system and information integrity controls are developed and documented;
    4. the system and information integrity procedures are disseminated to [Assignement: personnel or roles];
        1. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] system and information integrity policy addresses purpose;
        2. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] system and information integrity policy addresses scope;
        3. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] system and information integrity policy addresses roles;
        4. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] system and information integrity policy addresses responsibilities;
        5. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] system and information integrity policy addresses management commitment;
        6. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] system and information integrity policy addresses coordination among organizational entities;
        7. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] system and information integrity policy addresses compliance;
      1. the [Selection(one-or-more): organization-level; mission/business process-level; system-level] system and information integrity policy is consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines;
  1. the [Assignement: official] is designated to manage the development, documentation, and dissemination of the system and information integrity policy and procedures;
      1. the current system and information integrity policy is reviewed and updated [Assignement: frequency];
      2. the current system and information integrity policy is reviewed and updated following [Assignement: events];
      1. the current system and information integrity procedures are reviewed and updated [Assignement: frequency];
      2. the current system and information integrity procedures are reviewed and updated following [Assignement: events].

Assessment Method

Examine

System and information integrity policy system and information integrity procedures system security plan privacy plan other relevant documents or records

Interview

Organizational personnel with system and information integrity responsibilities organizational personnel with information security and privacy responsibilities
SI-02 Flaw Remediation

Control

  1. Identify, report, and correct system flaws;
  2. Test software and firmware updates related to flaw remediation for effectiveness and potential side effects before installation;
  3. Install security-relevant software and firmware updates within [Assignement: time period] of the release of the updates; and
  4. Incorporate flaw remediation into the organizational configuration management process.

Discussion

The need to remediate system flaws applies to all types of software and firmware. Organizations identify systems affected by software flaws, including potential vulnerabilities resulting from those flaws, and report this information to designated organizational personnel with information security and privacy responsibilities. Organizations consider establishing a controlled patching environment for mission-critical systems. Security-relevant updates include patches, service packs, and malicious code signatures. Organizations also address flaws discovered during assessments, continuous monitoring, incident response activities, and system error handling. By incorporating flaw remediation into configuration management processes, required remediation actions can be tracked and verified. Organization-defined time periods for updating security-relevant software and firmware may vary based on a variety of risk factors, including the security category of the system, the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw), the organizational risk tolerance, the mission supported by the system, or the threat environment. Some types of flaw remediation may require more testing than other types. Organizations determine the type of testing needed for the specific type of flaw remediation activity under consideration and the types of changes that are to be configuration-managed. Flaw remediation testing addresses both effectiveness of addressing security issues and for potential side effects on functionality, system and system component performance and operations. When implementing remediation activities, organizations consider the order and timing of updates to validate correct execution within the system environment, and to support system and component availability needs (i.e., implementing a staggered deployment strategy). In some situations, organizations may determine that the testing of software or firmware updates is not necessary or practical, such as when implementing simple malicious code signature updates. In testing decisions, organizations consider whether security-relevant software or firmware updates are obtained from authorized sources with appropriate digital signatures. When implementing remediation activities, organizations consider the order and timing of updates to validate correct execution within the system environment, and to support system and component availability needs (i.e., implementing a staggered deployment strategy). Organizations verify that software and firmware updates come from authorized sources prior to downloading.

Assessment Objective

    1. system flaws are identified;
    2. system flaws are reported;
    3. system flaws are corrected;
    1. software updates related to flaw remediation are tested for effectiveness before installation;
    2. software updates related to flaw remediation are tested for potential side effects before installation;
    3. firmware updates related to flaw remediation are tested for effectiveness before installation;
    4. firmware updates related to flaw remediation are tested for potential side effects before installation;
    1. security-relevant software updates are installed within [Assignement: time period] of the release of the updates;
    2. security-relevant firmware updates are installed within [Assignement: time period] of the release of the updates;
  1. flaw remediation is incorporated into the organizational configuration management process.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing flaw remediation procedures addressing configuration management list of flaws and vulnerabilities potentially affecting the system list of recent security flaw remediation actions performed on the system (e.g., list of installed patches, service packs, hot fixes, and other software updates to correct system flaws) test results from the installation of software and firmware updates to correct system flaws installation/change control records for security-relevant software and firmware updates system security plan privacy plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security and privacy responsibilities organizational personnel responsible for installing, configuring, and/or maintaining the system organizational personnel responsible for flaw remediation organizational personnel with configuration management responsibilities
SI-03 Malicious Code Protection

Control

  1. Implement [Selection(one-or-more): signature-based; non-signature-based] malicious code protection mechanisms at system entry and exit points to detect and eradicate malicious code;
  2. Automatically update malicious code protection mechanisms as new releases are available in accordance with organizational configuration management policy and procedures;
  3. Configure malicious code protection mechanisms to:
    1. Perform periodic scans of the system [Assignement: frequency] and real-time scans of files from external sources at [Selection(one-or-more): endpoint; network entry and exit points] as the files are downloaded, opened, or executed in accordance with organizational policy; and
    2. [Selection(one-or-more): block malicious code; quarantine malicious code; take {{ insert: param, si-03_odp.05 }} ] ; and send alert to [Assignement: personnel or roles] in response to malicious code detection; and
  4. Address the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system.

Discussion

System entry and exit points include firewalls, remote access servers, workstations, electronic mail servers, web servers, proxy servers, notebook computers, and mobile devices. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can also be encoded in various formats contained within compressed or hidden files or hidden in files using techniques such as steganography. Malicious code can be inserted into systems in a variety of ways, including by electronic mail, the world-wide web, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Malicious code protection mechanisms include both signature- and nonsignature-based technologies. Nonsignature-based detection mechanisms include artificial intelligence techniques that use heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide controls against such code for which signatures do not yet exist or for which existing signatures may not be effective. Malicious code for which active signatures do not yet exist or may be ineffective includes polymorphic malicious code (i.e., code that changes signatures when it replicates). Nonsignature-based mechanisms also include reputation-based technologies. In addition to the above technologies, pervasive configuration management, comprehensive software integrity controls, and anti-exploitation software may be effective in preventing the execution of unauthorized code. Malicious code may be present in commercial off-the-shelf software as well as custom-built software and could include logic bombs, backdoors, and other types of attacks that could affect organizational mission and business functions. In situations where malicious code cannot be detected by detection methods or technologies, organizations rely on other types of controls, including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to ensure that software does not perform functions other than the functions intended. Organizations may determine that, in response to the detection of malicious code, different actions may be warranted. For example, organizations can define actions in response to malicious code detection during periodic scans, the detection of malicious downloads, or the detection of maliciousness when attempting to open or execute files.

Assessment Objective

    1. [Selection(one-or-more): signature-based; non-signature-based] malicious code protection mechanisms are implemented at system entry and exit points to detect malicious code;
    2. [Selection(one-or-more): signature-based; non-signature-based] malicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code;
  1. malicious code protection mechanisms are updated automatically as new releases are available in accordance with organizational configuration management policy and procedures;
      1. malicious code protection mechanisms are configured to perform periodic scans of the system [Assignement: frequency];
      2. malicious code protection mechanisms are configured to perform real-time scans of files from external sources at [Selection(one-or-more): endpoint; network entry and exit points] as the files are downloaded, opened, or executed in accordance with organizational policy;
      1. malicious code protection mechanisms are configured to [Selection(one-or-more): block malicious code; quarantine malicious code; take {{ insert: param, si-03_odp.05 }} ] in response to malicious code detection;
      2. malicious code protection mechanisms are configured to send alerts to [Assignement: personnel or roles] in response to malicious code detection;
  2. the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system are addressed.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures configuration management policy and procedures procedures addressing malicious code protection malicious code protection mechanisms records of malicious code protection updates system design documentation system configuration settings and associated documentation scan results from malicious code protection mechanisms record of actions initiated by malicious code protection mechanisms in response to malicious code detection system audit records system security plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security responsibilities organizational personnel installing, configuring, and/or maintaining the system organizational personnel responsible for malicious code protection organizational personnel with configuration management responsibilities
SI-04 System Monitoring

Control

  1. Monitor the system to detect:
    1. Attacks and indicators of potential attacks in accordance with the following monitoring objectives: [Assignement: monitoring objectives] ; and
    2. Unauthorized local, network, and remote connections;
  2. Identify unauthorized use of the system through the following techniques and methods: [Assignement: techniques and methods];
  3. Invoke internal monitoring capabilities or deploy monitoring devices:
    1. Strategically within the system to collect organization-determined essential information; and
    2. At ad hoc locations within the system to track specific types of transactions of interest to the organization;
  4. Analyze detected events and anomalies;
  5. Adjust the level of system monitoring activity when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation;
  6. Obtain legal opinion regarding system monitoring activities; and
  7. Provide [Assignement: system monitoring information] to [Assignement: personnel or roles] [Selection(one-or-more): as needed; {{ insert: param, si-04_odp.06 }} ].

Discussion

System monitoring includes external and internal monitoring. External monitoring includes the observation of events occurring at external interfaces to the system. Internal monitoring includes the observation of events occurring within the system. Organizations monitor systems by observing audit activities in real time or by observing other system aspects such as access patterns, characteristics of access, and other actions. The monitoring objectives guide and inform the determination of the events. System monitoring capabilities are achieved through a variety of tools and techniques, including intrusion detection and prevention systems, malicious code protection software, scanning tools, audit record monitoring software, and network monitoring software. Depending on the security architecture, the distribution and configuration of monitoring devices may impact throughput at key internal and external boundaries as well as at other locations across a network due to the introduction of network throughput latency. If throughput management is needed, such devices are strategically located and deployed as part of an established organization-wide security architecture. Strategic locations for monitoring devices include selected perimeter locations and near key servers and server farms that support critical applications. Monitoring devices are typically employed at the managed interfaces associated with controls [SC-7](#sc-7) and [AC-17](#ac-17) . The information collected is a function of the organizational monitoring objectives and the capability of systems to support such objectives. Specific types of transactions of interest include Hypertext Transfer Protocol (HTTP) traffic that bypasses HTTP proxies. System monitoring is an integral part of organizational continuous monitoring and incident response programs, and output from system monitoring serves as input to those programs. System monitoring requirements, including the need for specific types of system monitoring, may be referenced in other controls (e.g., [AC-2g](#ac-2_smt.g), [AC-2(7)](#ac-2.7), [AC-2(12)(a)](#ac-2.12_smt.a), [AC-17(1)](#ac-17.1), [AU-13](#au-13), [AU-13(1)](#au-13.1), [AU-13(2)](#au-13.2), [CM-3f](#cm-3_smt.f), [CM-6d](#cm-6_smt.d), [MA-3a](#ma-3_smt.a), [MA-4a](#ma-4_smt.a), [SC-5(3)(b)](#sc-5.3_smt.b), [SC-7a](#sc-7_smt.a), [SC-7(24)(b)](#sc-7.24_smt.b), [SC-18b](#sc-18_smt.b), [SC-43b](#sc-43_smt.b) ). Adjustments to levels of system monitoring are based on law enforcement information, intelligence information, or other sources of information. The legality of system monitoring activities is based on applicable laws, executive orders, directives, regulations, policies, standards, and guidelines.

Assessment Objective

    1. the system is monitored to detect attacks and indicators of potential attacks in accordance with [Assignement: monitoring objectives];
      1. the system is monitored to detect unauthorized local connections;
      2. the system is monitored to detect unauthorized network connections;
      3. the system is monitored to detect unauthorized remote connections;
  1. unauthorized use of the system is identified through [Assignement: techniques and methods];
    1. internal monitoring capabilities are invoked or monitoring devices are deployed strategically within the system to collect organization-determined essential information;
    2. internal monitoring capabilities are invoked or monitoring devices are deployed at ad hoc locations within the system to track specific types of transactions of interest to the organization;
    1. detected events are analyzed;
    2. detected anomalies are analyzed;
  2. the level of system monitoring activity is adjusted when there is a change in risk to organizational operations and assets, individuals, other organizations, or the Nation;
  3. a legal opinion regarding system monitoring activities is obtained;
  4. [Assignement: system monitoring information] is provided to [Assignement: personnel or roles] [Selection(one-or-more): as needed; {{ insert: param, si-04_odp.06 }} ].

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing system monitoring tools and techniques continuous monitoring strategy facility diagram/layout system design documentation system monitoring tools and techniques documentation locations within the system where monitoring devices are deployed system configuration settings and associated documentation system security plan other relevant documents or records

Interview

System/network administrators organizational personnel with information security responsibilities organizational personnel installing, configuring, and/or maintaining the system organizational personnel responsible for monitoring the system
SI-05 Security Alerts, Advisories, and Directives

Control

  1. Receive system security alerts, advisories, and directives from [Assignement: external organizations] on an ongoing basis;
  2. Generate internal security alerts, advisories, and directives as deemed necessary;
  3. Disseminate security alerts, advisories, and directives to: [Selection(one-or-more): {{ insert: param, si-05_odp.03 }} ; {{ insert: param, si-05_odp.04 }} ; {{ insert: param, si-05_odp.05 }} ] ; and
  4. Implement security directives in accordance with established time frames, or notify the issuing organization of the degree of noncompliance.

Discussion

The Cybersecurity and Infrastructure Security Agency (CISA) generates security alerts and advisories to maintain situational awareness throughout the Federal Government. Security directives are issued by OMB or other designated organizations with the responsibility and authority to issue such directives. Compliance with security directives is essential due to the critical nature of many of these directives and the potential (immediate) adverse effects on organizational operations and assets, individuals, other organizations, and the Nation should the directives not be implemented in a timely manner. External organizations include supply chain partners, external mission or business partners, external service providers, and other peer or supporting organizations.

Assessment Objective

  1. system security alerts, advisories, and directives are received from [Assignement: external organizations] on an ongoing basis;
  2. internal security alerts, advisories, and directives are generated as deemed necessary;
  3. security alerts, advisories, and directives are disseminated to [Selection(one-or-more): {{ insert: param, si-05_odp.03 }} ; {{ insert: param, si-05_odp.04 }} ; {{ insert: param, si-05_odp.05 }} ];
  4. security directives are implemented in accordance with established time frames or if the issuing organization is notified of the degree of noncompliance.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing security alerts, advisories, and directives records of security alerts and advisories system security plan other relevant documents or records

Interview

Organizational personnel with security alert and advisory responsibilities organizational personnel implementing, operating, maintaining, and using the system organizational personnel, organizational elements, and/or external organizations to whom alerts, advisories, and directives are to be disseminated system/network administrators organizational personnel with information security responsibilities
SI-06 Security and Privacy Function Verification

Control

  1. Verify the correct operation of [Assignement: organization-defined security and privacy functions];
  2. Perform the verification of the functions specified in SI-6a [Selection(one-or-more): {{ insert: param, si-06_odp.04 }} ; upon command by user with appropriate privilege; {{ insert: param, si-06_odp.05 }} ];
  3. Alert [Assignement: personnel or roles] to failed security and privacy verification tests; and
  4. [Selection(one-or-more): shut the system down; restart the system; {{ insert: param, si-06_odp.08 }} ] when anomalies are discovered.

Discussion

Transitional states for systems include system startup, restart, shutdown, and abort. System notifications include hardware indicator lights, electronic alerts to system administrators, and messages to local computer consoles. In contrast to security function verification, privacy function verification ensures that privacy functions operate as expected and are approved by the senior agency official for privacy or that privacy attributes are applied or used as expected.

Assessment Objective

    1. [Assignement: security functions] are verified to be operating correctly;
    2. [Assignement: privacy functions] are verified to be operating correctly;
    1. [Assignement: security functions] are verified [Selection(one-or-more): {{ insert: param, si-06_odp.04 }} ; upon command by user with appropriate privilege; {{ insert: param, si-06_odp.05 }} ];
    2. [Assignement: privacy functions] are verified [Selection(one-or-more): {{ insert: param, si-06_odp.04 }} ; upon command by user with appropriate privilege; {{ insert: param, si-06_odp.05 }} ];
    1. [Assignement: personnel or roles] is/are alerted to failed security verification tests;
    2. [Assignement: personnel or roles] is/are alerted to failed privacy verification tests;
  1. [Selection(one-or-more): shut the system down; restart the system; {{ insert: param, si-06_odp.08 }} ] is/are initiated when anomalies are discovered.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing security and privacy function verification system design documentation system configuration settings and associated documentation alerts/notifications of failed security verification tests list of system transition states requiring security functionality verification system audit records system security plan privacy plan other relevant documents or records

Interview

Organizational personnel with security and privacy function verification responsibilities organizational personnel implementing, operating, and maintaining the system system/network administrators organizational personnel with information security and privacy responsibilities system developer
SI-07 Software, Firmware, and Information Integrity

Control

  1. Employ integrity verification tools to detect unauthorized changes to the following software, firmware, and information: [Assignement: organization-defined software, firmware, and information] ; and
  2. Take the following actions when unauthorized changes to the software, firmware, and information are detected: [Assignement: organization-defined actions].

Discussion

Unauthorized changes to software, firmware, and information can occur due to errors or malicious activity. Software includes operating systems (with key internal components, such as kernels or drivers), middleware, and applications. Firmware interfaces include Unified Extensible Firmware Interface (UEFI) and Basic Input/Output System (BIOS). Information includes personally identifiable information and metadata that contains security and privacy attributes associated with information. Integrity-checking mechanisms—including parity checks, cyclical redundancy checks, cryptographic hashes, and associated tools—can automatically monitor the integrity of systems and hosted applications.

Assessment Objective

    1. integrity verification tools are employed to detect unauthorized changes to [Assignement: software];
    2. integrity verification tools are employed to detect unauthorized changes to [Assignement: firmware];
    3. integrity verification tools are employed to detect unauthorized changes to [Assignement: information];
    1. [Assignement: actions] are taken when unauthorized changes to the software, are detected;
    2. [Assignement: actions] are taken when unauthorized changes to the firmware are detected;
    3. [Assignement: actions] are taken when unauthorized changes to the information are detected.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing software, firmware, and information integrity personally identifiable information processing policy system design documentation system configuration settings and associated documentation integrity verification tools and associated documentation records generated or triggered by integrity verification tools regarding unauthorized software, firmware, and information changes system audit records system security plan privacy plan other relevant documents or records

Interview

Organizational personnel responsible for software, firmware, and/or information integrity organizational personnel with information security and privacy responsibilities system/network administrators
SI-08 Spam Protection

Control

  1. Employ spam protection mechanisms at system entry and exit points to detect and act on unsolicited messages; and
  2. Update spam protection mechanisms when new releases are available in accordance with organizational configuration management policy and procedures.

Discussion

System entry and exit points include firewalls, remote-access servers, electronic mail servers, web servers, proxy servers, workstations, notebook computers, and mobile devices. Spam can be transported by different means, including email, email attachments, and web accesses. Spam protection mechanisms include signature definitions.

Assessment Objective

    1. spam protection mechanisms are employed at system entry points to detect unsolicited messages;
    2. spam protection mechanisms are employed at system exit points to detect unsolicited messages;
    3. spam protection mechanisms are employed at system entry points to act on unsolicited messages;
    4. spam protection mechanisms are employed at system exit points to act on unsolicited messages;
  1. spam protection mechanisms are updated when new releases are available in accordance with organizational configuration management policies and procedures.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures configuration management policies and procedures (CM-01) procedures addressing spam protection spam protection mechanisms records of spam protection updates system design documentation system configuration settings and associated documentation system audit records system security plan other relevant documents or records

Interview

Organizational personnel responsible for spam protection organizational personnel with information security responsibilities system/network administrators system developer
SI-09 Information Input Restrictions

Control

Discussion

Assessment Objective

Assessment Method

Examine

Interview

SI-10 Information Input Validation

Control

Check the validity of the following information inputs: [Assignement: information inputs].

Discussion

Checking the valid syntax and semantics of system inputs—including character set, length, numerical range, and acceptable values—verifies that inputs match specified definitions for format and content. For example, if the organization specifies that numerical values between 1-100 are the only acceptable inputs for a field in a given application, inputs of "387," "abc," or "%K%" are invalid inputs and are not accepted as input to the system. Valid inputs are likely to vary from field to field within a software application. Applications typically follow well-defined protocols that use structured messages (i.e., commands or queries) to communicate between software modules or system components. Structured messages can contain raw or unstructured data interspersed with metadata or control information. If software applications use attacker-supplied inputs to construct structured messages without properly encoding such messages, then the attacker could insert malicious commands or special characters that can cause the data to be interpreted as control information or metadata. Consequently, the module or component that receives the corrupted output will perform the wrong operations or otherwise interpret the data incorrectly. Prescreening inputs prior to passing them to interpreters prevents the content from being unintentionally interpreted as commands. Input validation ensures accurate and correct inputs and prevents attacks such as cross-site scripting and a variety of injection attacks.

Assessment Objective

the validity of the [Assignement: information inputs] is checked.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures access control policy and procedures separation of duties policy and procedures procedures addressing information input validation documentation for automated tools and applications to verify the validity of information list of information inputs requiring validity checks system design documentation system configuration settings and associated documentation system audit records system security plan other relevant documents or records

Interview

Organizational personnel responsible for information input validation organizational personnel with information security responsibilities system/network administrators system developer
SI-11 Error Handling

Control

  1. Generate error messages that provide information necessary for corrective actions without revealing information that could be exploited; and
  2. Reveal error messages only to [Assignement: personnel or roles].

Discussion

Organizations consider the structure and content of error messages. The extent to which systems can handle error conditions is guided and informed by organizational policy and operational requirements. Exploitable information includes stack traces and implementation details; erroneous logon attempts with passwords mistakenly entered as the username; mission or business information that can be derived from, if not stated explicitly by, the information recorded; and personally identifiable information, such as account numbers, social security numbers, and credit card numbers. Error messages may also provide a covert channel for transmitting information.

Assessment Objective

  1. error messages that provide the information necessary for corrective actions are generated without revealing information that could be exploited;
  2. error messages are revealed only to [Assignement: personnel or roles].

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing system error handling system design documentation system configuration settings and associated documentation documentation providing the structure and content of error messages system audit records system security plan other relevant documents or records

Interview

Organizational personnel responsible for information input validation organizational personnel with information security responsibilities system/network administrators system developer
SI-12 Information Management and Retention

Control

Manage and retain information within the system and information output from the system in accordance with applicable laws, executive orders, directives, regulations, policies, standards, guidelines and operational requirements.

Discussion

Information management and retention requirements cover the full life cycle of information, in some cases extending beyond system disposal. Information to be retained may also include policies, procedures, plans, reports, data output from control implementation, and other types of administrative information. The National Archives and Records Administration (NARA) provides federal policy and guidance on records retention and schedules. If organizations have a records management office, consider coordinating with records management personnel. Records produced from the output of implemented controls that may require management and retention include, but are not limited to: All XX-1, [AC-6(9)](#ac-6.9), [AT-4](#at-4), [AU-12](#au-12), [CA-2](#ca-2), [CA-3](#ca-3), [CA-5](#ca-5), [CA-6](#ca-6), [CA-7](#ca-7), [CA-8](#ca-8), [CA-9](#ca-9), [CM-2](#cm-2), [CM-3](#cm-3), [CM-4](#cm-4), [CM-6](#cm-6), [CM-8](#cm-8), [CM-9](#cm-9), [CM-12](#cm-12), [CM-13](#cm-13), [CP-2](#cp-2), [IR-6](#ir-6), [IR-8](#ir-8), [MA-2](#ma-2), [MA-4](#ma-4), [PE-2](#pe-2), [PE-8](#pe-8), [PE-16](#pe-16), [PE-17](#pe-17), [PL-2](#pl-2), [PL-4](#pl-4), [PL-7](#pl-7), [PL-8](#pl-8), [PM-5](#pm-5), [PM-8](#pm-8), [PM-9](#pm-9), [PM-18](#pm-18), [PM-21](#pm-21), [PM-27](#pm-27), [PM-28](#pm-28), [PM-30](#pm-30), [PM-31](#pm-31), [PS-2](#ps-2), [PS-6](#ps-6), [PS-7](#ps-7), [PT-2](#pt-2), [PT-3](#pt-3), [PT-7](#pt-7), [RA-2](#ra-2), [RA-3](#ra-3), [RA-5](#ra-5), [RA-8](#ra-8), [SA-4](#sa-4), [SA-5](#sa-5), [SA-8](#sa-8), [SA-10](#sa-10), [SI-4](#si-4), [SR-2](#sr-2), [SR-4](#sr-4), [SR-8](#sr-8).

Assessment Objective

  1. information within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements;
  2. information within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements;
  3. information output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements;
  4. information output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures personally identifiable information processing policy records retention and disposition policy records retention and disposition procedures federal laws, Executive Orders, directives, policies, regulations, standards, and operational requirements applicable to information management and retention media protection policy media protection procedures audit findings system security plan privacy plan privacy program plan personally identifiable information inventory privacy impact assessment privacy risk assessment documentation other relevant documents or records

Interview

Organizational personnel with information and records management, retention, and disposition responsibilities organizational personnel with information security and privacy responsibilities network administrators
SI-13 Predictable Failure Prevention

Control

  1. Determine mean time to failure (MTTF) for the following system components in specific environments of operation: [Assignement: system components] ; and
  2. Provide substitute system components and a means to exchange active and standby components in accordance with the following criteria: [Assignement: mean time to failure (MTTF) substitution criteria].

Discussion

While MTTF is primarily a reliability issue, predictable failure prevention is intended to address potential failures of system components that provide security capabilities. Failure rates reflect installation-specific consideration rather than the industry-average. Organizations define the criteria for the substitution of system components based on the MTTF value with consideration for the potential harm from component failures. The transfer of responsibilities between active and standby components does not compromise safety, operational readiness, or security capabilities. The preservation of system state variables is also critical to help ensure a successful transfer process. Standby components remain available at all times except for maintenance issues or recovery failures in progress.

Assessment Objective

  1. mean time to failure (MTTF) is determined for [Assignement: system components] in specific environments of operation;
  2. substitute system components and a means to exchange active and standby components are provided in accordance with [Assignement: mean time to failure (MTTF) substitution criteria].

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing predictable failure prevention system design documentation system configuration settings and associated documentation list of MTTF substitution criteria system audit records system security plan other relevant documents or records

Interview

Organizational personnel responsible for MTTF determinations and activities organizational personnel with information security responsibilities system/network administrators organizational personnel with contingency planning responsibilities
SI-14 Non-persistence

Control

Implement non-persistent [Assignement: system components and services] that are initiated in a known state and terminated [Selection(one-or-more): upon end of session of use; {{ insert: param, si-14_odp.03 }} ].

Discussion

Implementation of non-persistent components and services mitigates risk from advanced persistent threats (APTs) by reducing the targeting capability of adversaries (i.e., window of opportunity and available attack surface) to initiate and complete attacks. By implementing the concept of non-persistence for selected system components, organizations can provide a trusted, known state computing resource for a specific time period that does not give adversaries sufficient time to exploit vulnerabilities in organizational systems or operating environments. Since the APT is a high-end, sophisticated threat with regard to capability, intent, and targeting, organizations assume that over an extended period, a percentage of attacks will be successful. Non-persistent system components and services are activated as required using protected information and terminated periodically or at the end of sessions. Non-persistence increases the work factor of adversaries attempting to compromise or breach organizational systems. Non-persistence can be achieved by refreshing system components, periodically reimaging components, or using a variety of common virtualization techniques. Non-persistent services can be implemented by using virtualization techniques as part of virtual machines or as new instances of processes on physical machines (either persistent or non-persistent). The benefit of periodic refreshes of system components and services is that it does not require organizations to first determine whether compromises of components or services have occurred (something that may often be difficult to determine). The refresh of selected system components and services occurs with sufficient frequency to prevent the spread or intended impact of attacks, but not with such frequency that it makes the system unstable. Refreshes of critical components and services may be done periodically to hinder the ability of adversaries to exploit optimum windows of vulnerabilities.

Assessment Objective

  1. non-persistent [Assignement: system components and services] that are initiated in a known state are implemented;
  2. non-persistent [Assignement: system components and services] are terminated [Selection(one-or-more): upon end of session of use; {{ insert: param, si-14_odp.03 }} ].

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing non-persistence for system components system design documentation system configuration settings and associated documentation system audit records system security plan other relevant documents or records

Interview

Organizational personnel responsible for non-persistence organizational personnel with information security responsibilities system/network administrators system developer
SI-15 Information Output Filtering

Control

Validate information output from the following software programs and/or applications to ensure that the information is consistent with the expected content: [Assignement: software programs and/or applications].

Discussion

Certain types of attacks, including SQL injections, produce output results that are unexpected or inconsistent with the output results that would be expected from software programs or applications. Information output filtering focuses on detecting extraneous content, preventing such extraneous content from being displayed, and then alerting monitoring tools that anomalous behavior has been discovered.

Assessment Objective

information output from [Assignement: software programs and/or applications] is validated to ensure that the information is consistent with the expected content.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing information output filtering system design documentation system configuration settings and associated documentation system audit records system security plan other relevant documents or records

Interview

Organizational personnel responsible for validating information output organizational personnel with information security responsibilities system/network administrators system developer
SI-16 Memory Protection

Control

Implement the following controls to protect the system memory from unauthorized code execution: [Assignement: controls].

Discussion

Some adversaries launch attacks with the intent of executing code in non-executable regions of memory or in memory locations that are prohibited. Controls employed to protect memory include data execution prevention and address space layout randomization. Data execution prevention controls can either be hardware-enforced or software-enforced with hardware enforcement providing the greater strength of mechanism.

Assessment Objective

[Assignement: controls] are implemented to protect the system memory from unauthorized code execution.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures procedures addressing memory protection for the system system design documentation system configuration settings and associated documentation list of security safeguards protecting system memory from unauthorized code execution system audit records system security plan other relevant documents or records

Interview

Organizational personnel responsible for memory protection organizational personnel with information security responsibilities system/network administrators system developer
SI-17 Fail-safe Procedures

Control

Implement the indicated fail-safe procedures when the indicated failures occur: [Assignement: organization-defined list of failure conditions and associated fail-safe procedures].

Discussion

Failure conditions include the loss of communications among critical system components or between system components and operational facilities. Fail-safe procedures include alerting operator personnel and providing specific instructions on subsequent steps to take. Subsequent steps may include doing nothing, reestablishing system settings, shutting down processes, restarting the system, or contacting designated organizational personnel.

Assessment Objective

[Assignement: fail-safe procedures] are implemented when [Assignement: list of failure conditions] occur.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures documentation addressing fail-safe procedures for the system system design documentation system configuration settings and associated documentation list of security safeguards protecting the system memory from unauthorized code execution system audit records system security plan other relevant documents or records

Interview

Organizational personnel responsible for fail-safe procedures organizational personnel with information security responsibilities system/network administrators system developer
SI-18 Personally Identifiable Information Quality Operations

Control

  1. Check the accuracy, relevance, timeliness, and completeness of personally identifiable information across the information life cycle [Assignement: organization-defined frequency] ; and
  2. Correct or delete inaccurate or outdated personally identifiable information.

Discussion

Personally identifiable information quality operations include the steps that organizations take to confirm the accuracy and relevance of personally identifiable information throughout the information life cycle. The information life cycle includes the creation, collection, use, processing, storage, maintenance, dissemination, disclosure, and disposal of personally identifiable information. Personally identifiable information quality operations include editing and validating addresses as they are collected or entered into systems using automated address verification look-up application programming interfaces. Checking personally identifiable information quality includes the tracking of updates or changes to data over time, which enables organizations to know how and what personally identifiable information was changed should erroneous information be identified. The measures taken to protect personally identifiable information quality are based on the nature and context of the personally identifiable information, how it is to be used, how it was obtained, and the potential de-identification methods employed. The measures taken to validate the accuracy of personally identifiable information used to make determinations about the rights, benefits, or privileges of individuals covered under federal programs may be more comprehensive than the measures used to validate personally identifiable information used for less sensitive purposes.

Assessment Objective

    1. the accuracy of personally identifiable information across the information life cycle is checked [Assignement: frequency];
    2. the relevance of personally identifiable information across the information life cycle is checked [Assignement: frequency];
    3. the timeliness of personally identifiable information across the information life cycle is checked [Assignement: frequency];
    4. the completeness of personally identifiable information across the information life cycle is checked [Assignement: frequency];
  1. inaccurate or outdated personally identifiable information is corrected or deleted.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures personally identifiable information processing policy documentation addressing personally identifiable information quality operations quality reports maintenance logs system audit records audit findings system security plan privacy plan privacy impact assessment privacy risk assessment documentation other relevant documents or records

Interview

Organizational personnel responsible for performing personally identifiable information quality inspections organizational personnel with information security responsibilities organizational personnel with privacy responsibilities
SI-19 De-identification

Control

  1. Remove the following elements of personally identifiable information from datasets: [Assignement: elements] ; and
  2. Evaluate [Assignement: frequency] for effectiveness of de-identification.

Discussion

De-identification is the general term for the process of removing the association between a set of identifying data and the data subject. Many datasets contain information about individuals that can be used to distinguish or trace an individual’s identity, such as name, social security number, date and place of birth, mother’s maiden name, or biometric records. Datasets may also contain other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information. Personally identifiable information is removed from datasets by trained individuals when such information is not (or no longer) necessary to satisfy the requirements envisioned for the data. For example, if the dataset is only used to produce aggregate statistics, the identifiers that are not needed for producing those statistics are removed. Removing identifiers improves privacy protection since information that is removed cannot be inadvertently disclosed or improperly used. Organizations may be subject to specific de-identification definitions or methods under applicable laws, regulations, or policies. Re-identification is a residual risk with de-identified data. Re-identification attacks can vary, including combining new datasets or other improvements in data analytics. Maintaining awareness of potential attacks and evaluating for the effectiveness of the de-identification over time support the management of this residual risk.

Assessment Objective

  1. [Assignement: elements] are removed from datasets;
  2. the effectiveness of de-identification is evaluated [Assignement: frequency].

Assessment Method

Examine

System and information integrity policy system and information integrity procedures personally identifiable information processing policy de-identification procedures system configuration datasets with personally identifiable information removed system security plan privacy plan privacy impact assessment privacy risk assessment documentation other relevant documents or records

Interview

Organizational personnel responsible for identifying unnecessary identifiers organizational personnel responsible for removing personally identifiable information from datasets organizational personnel with information security and privacy responsibilities
SI-20 Tainting

Control

Embed data or capabilities in the following systems or system components to determine if organizational data has been exfiltrated or improperly removed from the organization: [Assignement: systems or system components].

Discussion

Many cyber-attacks target organizational information, or information that the organization holds on behalf of other entities (e.g., personally identifiable information), and exfiltrate that data. In addition, insider attacks and erroneous user procedures can remove information from the system that is in violation of the organizational policies. Tainting approaches can range from passive to active. A passive tainting approach can be as simple as adding false email names and addresses to an internal database. If the organization receives email at one of the false email addresses, it knows that the database has been compromised. Moreover, the organization knows that the email was sent by an unauthorized entity, so any packets it includes potentially contain malicious code, and that the unauthorized entity may have potentially obtained a copy of the database. Another tainting approach can include embedding false data or steganographic data in files to enable the data to be found via open-source analysis. Finally, an active tainting approach can include embedding software in the data that is able to "call home," thereby alerting the organization to its "capture," and possibly its location, and the path by which it was exfiltrated or removed.

Assessment Objective

data or capabilities are embedded in [Assignement: systems or system components] to determine if organizational data has been exfiltrated or improperly removed from the organization.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures personally identifiable information processing policy procedures addressing software and information integrity system design documentation system configuration settings and associated documentation policy and procedures addressing the systems security engineering technique of deception system security plan privacy plan other relevant documents or records

Interview

Organizational personnel responsible for detecting tainted data organizational personnel with systems security engineering responsibilities organizational personnel with information security and privacy responsibilities
SI-21 Information Refresh

Control

Refresh [Assignement: information] at [Assignement: frequencies] or generate the information on demand and delete the information when no longer needed.

Discussion

Retaining information for longer than it is needed makes it an increasingly valuable and enticing target for adversaries. Keeping information available for the minimum period of time needed to support organizational missions or business functions reduces the opportunity for adversaries to compromise, capture, and exfiltrate that information.

Assessment Objective

the [Assignement: information] is refreshed [Assignement: frequencies] or is generated on demand and deleted when no longer needed.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures personally identifiable information processing policy procedures addressing software and information integrity system design documentation system configuration settings and associated documentation information refresh procedures list of information to be refreshed system security plan privacy plan other relevant documents or records

Interview

Organizational personnel responsible for refreshing information organizational personnel with information security and privacy responsibilities organizational personnel with systems security engineering responsibilities system developers
SI-22 Information Diversity

Control

  1. Identify the following alternative sources of information for [Assignement: essential functions and services]: [Assignement: alternative information sources] ; and
  2. Use an alternative information source for the execution of essential functions or services on [Assignement: systems or system components] when the primary source of information is corrupted or unavailable.

Discussion

Actions taken by a system service or a function are often driven by the information it receives. Corruption, fabrication, modification, or deletion of that information could impact the ability of the service function to properly carry out its intended actions. By having multiple sources of input, the service or function can continue operation if one source is corrupted or no longer available. It is possible that the alternative sources of information may be less precise or less accurate than the primary source of information. But having such sub-optimal information sources may still provide a sufficient level of quality that the essential service or function can be carried out, even in a degraded or debilitated manner.

Assessment Objective

  1. [Assignement: alternative information sources] for [Assignement: essential functions and services] are identified;
  2. an alternative information source is used for the execution of essential functions or services on [Assignement: systems or system components] when the primary source of information is corrupted or unavailable.

Assessment Method

Examine

System and information integrity policy system and information integrity procedures personally identifiable information processing policy system design documentation system configuration settings and associated documentation list of information sources system security plan privacy plan other relevant documents or records

Interview

Organizational personnel with information security and privacy responsibilities organizational personnel with systems security engineering responsibilities system developers
SI-23 Information Fragmentation

Control

Based on [Assignement: circumstances]:
  1. Fragment the following information: [Assignement: information] ; and
  2. Distribute the fragmented information across the following systems or system components: [Assignement: systems or system components].

Discussion

One objective of the advanced persistent threat is to exfiltrate valuable information. Once exfiltrated, there is generally no way for the organization to recover the lost information. Therefore, organizations may consider dividing the information into disparate elements and distributing those elements across multiple systems or system components and locations. Such actions will increase the adversary’s work factor to capture and exfiltrate the desired information and, in so doing, increase the probability of detection. The fragmentation of information impacts the organization’s ability to access the information in a timely manner. The extent of the fragmentation is dictated by the impact or classification level (and value) of the information, threat intelligence information received, and whether data tainting is used (i.e., data tainting-derived information about the exfiltration of some information could result in the fragmentation of the remaining information).

Assessment Objective

  1. under [Assignement: circumstances], [Assignement: information] is fragmented;
  2. under [Assignement: circumstances] , the fragmented information is distributed across [Assignement: systems or system components].

Assessment Method

Examine

System and information integrity policy system and information integrity procedures personally identifiable information processing policy procedures addressing software and information integrity system design documentation system configuration settings and associated documentation procedures to identify information for fragmentation and distribution across systems/system components list of distributed and fragmented information list of circumstances requiring information fragmentation enterprise architecture system security architecture system security plan privacy plan other relevant documents or records

Interview

Organizational personnel with information security and privacy responsibilities organizational personnel with systems security engineering responsibilities system developers security architects

1.1 Odkazy

1.2 Identifikované požadavky

1.3 Související regulace

2. Identifikované požadavky

Požadavky
Zdroj Požadavek

3. Související regulace

Regulace
Zdroj Regulace