Az Policy Advertizer

IR-4

FedRAMP_High_R4_IR-4

FedRAMP High IR-4

Incident Response

Incident Handling

Shared

n/a

The organization: a. Implements an incident handling capability for security incidents that includes preparation, detection and analysis, containment, eradication, and recovery; b. Coordinates incident handling activities with contingency planning activities; and c. Incorporates lessons learned from ongoing incident handling activities into incident response procedures, training, and testing/exercises, and implements the resulting changes accordingly. Supplemental Guidance: Organizations recognize that incident response capability is dependent on the capabilities of organizational information systems and the mission/business processes being supported by those systems. Therefore, organizations consider incident response as part of the definition, design, and development of mission/business processes and information systems. Incident-related information can be obtained from a variety of sources including, for example, audit monitoring, network monitoring, physical access monitoring, user/administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including, for example, mission/business owners, information system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive (function). Related controls: AU-6, CM-6, CP-2, CP-4, IR-2, IR-3, IR-8, PE-6, SC-5, SC-7, SI-3, SI-4, SI-7. References: Executive Order 13587; NIST Special Publication 800-61.

IR-4(1)

FedRAMP_High_R4_IR-4(1)

FedRAMP High IR-4 (1)

Incident Response

Automated Incident Handling Processes

Shared

n/a

The organization employs automated mechanisms to support the incident handling process. Supplemental Guidance: Automated mechanisms supporting incident handling processes include, for example, online incident management systems.

IR-4(4)

FedRAMP_High_R4_IR-4(4)

FedRAMP High IR-4 (4)

Incident Response

Information Correlation

Shared

n/a

The organization correlates incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response. Supplemental Guidance: Sometimes the nature of a threat event, for example, a hostile cyber attack, is such that it can only be observed by bringing together information from different sources including various reports and reporting procedures established by organizations.

IR-7(1)

FedRAMP_High_R4_IR-7(1)

FedRAMP High IR-7 (1)

Incident Response

Automation Support For Availability Of Information / Support

Shared

n/a

The organization employs automated mechanisms to increase the availability of incident response- related information and support. Supplemental Guidance: Automated mechanisms can provide a push and/or pull capability for users to obtain incident response assistance. For example, individuals might have access to a website to query the assistance capability, or conversely, the assistance capability may have the ability to proactively send information to users (general distribution or targeted) as part of increasing understanding of current response capabilities and support.

IR-8

FedRAMP_High_R4_IR-8

FedRAMP High IR-8

Incident Response

Incident Response Plan

Shared

n/a

The organization: a. Develops an incident response plan that: 1. Provides the organization with a roadmap for implementing its incident response capability; 2. Describes the structure and organization of the incident response capability; 3. Provides a high-level approach for how the incident response capability fits into the overall organization; 4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions; 5. Defines reportable incidents; 6. Provides metrics for measuring the incident response capability within the organization; 7. Defines the resources and management support needed to effectively maintain and mature an incident response capability; and 8. Is reviewed and approved by [Assignment: organization-defined personnel or roles]; b. Distributes copies of the incident response plan to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; c. Reviews the incident response plan [Assignment: organization-defined frequency]; d. Updates the incident response plan to address system/organizational changes or problems encountered during plan implementation, execution, or testing; e. Communicates incident response plan changes to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and f. Protects the incident response plan from unauthorized disclosure and modification. Supplemental Guidance: It is important that organizations develop and implement a coordinated approach to incident response. Organizational missions, business functions, strategies, goals, and objectives for incident response help to determine the structure of incident response capabilities. As part of a comprehensive incident response capability, organizations consider the coordination and sharing of information with external organizations, including, for example, external service providers and organizations involved in the supply chain for organizational information systems. Related controls: MP-2, MP-4, MP-5. Control Enhancements: None. References: NIST Special Publication 800-61.

IR-4

FedRAMP_Moderate_R4_IR-4

FedRAMP Moderate IR-4

Incident Response

Incident Handling

Shared

n/a

FedRAMP_Moderate_R4_IR-4(1)

IR-4(1)

FedRAMP Moderate IR-4 (1)

Incident Response

Automated Incident Handling Processes

Shared

n/a

FedRAMP_Moderate_R4_IR-7(1)

IR-7(1)

FedRAMP Moderate IR-7 (1)

Incident Response

Automation Support For Availability Of Information / Support

Shared

n/a

IR-8

FedRAMP_Moderate_R4_IR-8

FedRAMP Moderate IR-8

Incident Response

Incident Response Plan

Shared

n/a

hipaa-1501.02f1Organizational.123-02.f

1501.02f1Organizational.123-02.f

1501.02f1Organizational.123-02.f

15 Incident Management

1501.02f1Organizational.123-02.f 02.03 During Employment

Shared

n/a

Sanctions are fairly applied to employees following violations of the information security policies once a breach is verified and includes consideration of multiple factors. The organization documents personnel involved in incidents, steps taken, and the timeline associated with those steps, steps taken for notification, the rationale for discipline, and the final outcome for each incident.

hipaa-1503.02f2Organizational.12-02.f

1503.02f2Organizational.12-02.f

1503.02f2Organizational.12-02.f

15 Incident Management

1503.02f2Organizational.12-02.f 02.03 During Employment

Shared

n/a

A contact in HR is appointed to handle employee security incidents and notify the CISO or a designated representative of the application of a formal employee sanctions process, identifying the individual and the reason for the sanction.

hipaa-1504.06e1Organizational.34-06.e

1504.06e1Organizational.34-06.e

1504.06e1Organizational.34-06.e

15 Incident Management

1504.06e1Organizational.34-06.e 06.01 Compliance with Legal Requirements

Shared

n/a

Management approves the use of information assets and takes appropriate action when unauthorized activity occurs.

hipaa-1505.11a1Organizational.13-11.a

1505.11a1Organizational.13-11.a

1505.11a1Organizational.13-11.a

15 Incident Management

1505.11a1Organizational.13-11.a 11.01 Reporting Information Security Incidents and Weaknesses

Shared

n/a

A formal security incident response program has been established to respond, report (without fear of repercussion), escalate and treat breaches and reported security events or incidents. Organization-wide standards are specified for the time required for system administrators and other personnel to report anomalous events to the incident handling team, the mechanisms for such reporting, and the kind of information that should be included in the incident notification. This reporting includes notifying internal and external stakeholders, the appropriate community Computer Emergency Response Team, and law enforcement agencies in accordance with all legal or regulatory requirements for involving such organizations in computer incidents.

hipaa-1506.11a1Organizational.2-11.a

1506.11a1Organizational.2-11.a

1506.11a1Organizational.2-11.a

15 Incident Management

1506.11a1Organizational.2-11.a 11.01 Reporting Information Security Incidents and Weaknesses

Shared

n/a

There is a point of contact for reporting information security events who is made known throughout the organization, always available, and able to provide adequate and timely response. The organization also maintains a list of third-party contact information (e.g., the email addresses of their information security officers), which can be used to report a security incident.

hipaa-1508.11a2Organizational.1-11.a

1508.11a2Organizational.1-11.a

1508.11a2Organizational.1-11.a

15 Incident Management

1508.11a2Organizational.1-11.a 11.01 Reporting Information Security Incidents and Weaknesses

Shared

n/a

The organization provides a process/mechanism to anonymously report security issues.

hipaa-1509.11a2Organizational.236-11.a

1509.11a2Organizational.236-11.a

1509.11a2Organizational.236-11.a

15 Incident Management

1509.11a2Organizational.236-11.a 11.01 Reporting Information Security Incidents and Weaknesses

Shared

n/a

The incident management program formally defines information security incidents and the phases of incident response; roles and responsibilities; incident handling, reporting and communication processes; third-party relationships and the handling of third-party breaches; and the supporting forensics program. The organization formally assigns job titles and duties for handling computer and network security incidents to specific individuals and identifies management personnel who will support the incident handling process by acting in key decision-making roles.

hipaa-1510.11a2Organizational.47-11.a

1510.11a2Organizational.47-11.a

1510.11a2Organizational.47-11.a

15 Incident Management

1510.11a2Organizational.47-11.a 11.01 Reporting Information Security Incidents and Weaknesses

Shared

n/a

Reports and communications are made without unreasonable delay and no later than 60 days after the discovery of an incident, unless otherwise stated by law enforcement orally or in writing, and include the necessary elements.

hipaa-1511.11a2Organizational.5-11.a

1511.11a2Organizational.5-11.a

1511.11a2Organizational.5-11.a

15 Incident Management

1511.11a2Organizational.5-11.a 11.01 Reporting Information Security Incidents and Weaknesses

Shared

n/a

All employees, contractors and third-party users receive mandatory incident response training to ensure they are aware of their responsibilities to report information security events as quickly as possible, the procedure for reporting information security events, and the point(s) of contact, including the incident response team, and the contact information is published and made readily available.

hipaa-1515.11a3Organizational.3-11.a

1515.11a3Organizational.3-11.a

1515.11a3Organizational.3-11.a

15 Incident Management

1515.11a3Organizational.3-11.a 11.01 Reporting Information Security Incidents and Weaknesses

Shared

n/a

Incidents (or a sample of incidents) are reviewed to identify necessary improvement to the security controls.

hipaa-1516.11c1Organizational.12-11.c

1516.11c1Organizational.12-11.c

1516.11c1Organizational.12-11.c

15 Incident Management

1516.11c1Organizational.12-11.c 11.02 Management of Information Security Incidents and Improvements

Shared

n/a

The security incident response program accounts for and prepares the organization for a variety of incidents.

hipaa-1517.11c1Organizational.3-11.c

1517.11c1Organizational.3-11.c

1517.11c1Organizational.3-11.c

15 Incident Management

1517.11c1Organizational.3-11.c 11.02 Management of Information Security Incidents and Improvements

Shared

n/a

There is a point of contact who is responsible for coordinating incident responses and has the authority to direct actions required in all phases of the incident response process.

hipaa-1520.11c2Organizational.4-11.c

1520.11c2Organizational.4-11.c

1520.11c2Organizational.4-11.c

15 Incident Management

1520.11c2Organizational.4-11.c 11.02 Management of Information Security Incidents and Improvements

Shared

n/a

The incident response plan is communicated to the appropriate individuals throughout the organization.

hipaa-1521.11c2Organizational.56-11.c

1521.11c2Organizational.56-11.c

1521.11c2Organizational.56-11.c

15 Incident Management

1521.11c2Organizational.56-11.c 11.02 Management of Information Security Incidents and Improvements

Shared

n/a

Testing exercises are planned, coordinated, executed, and documented periodically, at least annually, using reviews, analyses, and simulations to determine incident response effectiveness. Testing includes personnel associated with the incident handling team to ensure that they understand current threats and risks, as well as their responsibilities in supporting the incident handling team.

hipaa-1522.11c3Organizational.13-11.c

1522.11c3Organizational.13-11.c

1522.11c3Organizational.13-11.c

15 Incident Management

1522.11c3Organizational.13-11.c 11.02 Management of Information Security Incidents and Improvements

Shared

n/a

An incident response support resource, who is an integral part of the organization's incident response capability, is available to offer advice and assistance to users of information systems for the handling and reporting of security incidents in a timely manner.

hipaa-1560.11d1Organizational.1-11.d

1560.11d1Organizational.1-11.d

1560.11d1Organizational.1-11.d

15 Incident Management

1560.11d1Organizational.1-11.d 11.02 Management of Information Security Incidents and Improvements

Shared

n/a

The information gained from the evaluation of information security incidents is used to identify recurring or high-impact incidents, and update the incident response and recovery strategy.

A.16.1.1

ISO27001-2013_A.16.1.1

ISO 27001:2013 A.16.1.1

Information Security Incident Management

Responsibilities and procedures

Shared

n/a

Management responsibilities and procedures shall be established to ensure a quick, effective and orderly response to information security incidents.

A.16.1.2

ISO27001-2013_A.16.1.2

ISO 27001:2013 A.16.1.2

Information Security Incident Management

Reporting information security events

Shared

n/a

Information security events shall be reported through appropriate management channels as quickly as possible.

A.16.1.4

ISO27001-2013_A.16.1.4

ISO 27001:2013 A.16.1.4

Information Security Incident Management

Assessment of and decision on information security events

Shared

n/a

Information security events shall be assessed and it shall be decided if they are to be classified as information security incidents.

A.16.1.5

ISO27001-2013_A.16.1.5

ISO 27001:2013 A.16.1.5

Information Security Incident Management

Response to information security incidents

Shared

n/a

Information security incidents shall be responded to in accordance with the documented procedures.

A.16.1.6

ISO27001-2013_A.16.1.6

ISO 27001:2013 A.16.1.6

Information Security Incident Management

Learning from information security incidents

Shared

n/a

Knowledge gained from analyzing and resolving information security incidents shall be used to reduce the likelihood or impact of future incidents.

A.16.1.7

ISO27001-2013_A.16.1.7

ISO 27001:2013 A.16.1.7

Information Security Incident Management

Collection of evidence

Shared

n/a

The organization shall define and apply procedures for the identification, collection, acquisition and preservation of information which can serve as evidence.

NIST_SP_800-171_R2_3

.6.1

NIST_SP_800-171_R2_3.6.1

NIST SP 800-171 R2 3.6.1

Incident response

Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.

Shared

Microsoft and the customer share responsibilities for implementing this requirement.

Organizations recognize that incident handling capability is dependent on the capabilities of organizational systems and the mission/business processes being supported by those systems. Organizations consider incident handling as part of the definition, design, and development of mission/business processes and systems. Incident-related information can be obtained from a variety of sources including audit monitoring, network monitoring, physical access monitoring, user and administrator reports, and reported supply chain events. Effective incident handling capability includes coordination among many organizational entities including mission/business owners, system owners, authorizing officials, human resources offices, physical and personnel security offices, legal departments, operations personnel, procurement offices, and the risk executive. As part of user response activities, incident response training is provided by organizations and is linked directly to the assigned roles and responsibilities of organizational personnel to ensure that the appropriate content and level of detail is included in such training. For example, regular users may only need to know who to call or how to recognize an incident on the system; system administrators may require additional training on how to handle or remediate incidents; and incident responders may receive more specific training on forensics, reporting, system recovery, and restoration. Incident response training includes user training in the identification/reporting of suspicious activities from external and internal sources. User response activities also includes incident response assistance which may consist of help desk support, assistance groups, and access to forensics services or consumer redress services, when required. [SP 800-61] provides guidance on incident handling. [SP 800-86] and [SP 800-101] provide guidance on integrating forensic techniques into incident response. [SP 800-161] provides guidance on supply chain risk management.

IR-4

NIST_SP_800-53_R4_IR-4

NIST SP 800-53 Rev. 4 IR-4

Incident Response

Incident Handling

Shared

n/a

NIST_SP_800-53_R4_IR-4(1)

IR-4(1)

NIST SP 800-53 Rev. 4 IR-4 (1)

Incident Response

Automated Incident Handling Processes

Shared

n/a

NIST_SP_800-53_R4_IR-4(4)

IR-4(4)

NIST SP 800-53 Rev. 4 IR-4 (4)

Incident Response

Information Correlation

Shared

n/a

NIST_SP_800-53_R4_IR-7(1)

IR-7(1)

NIST SP 800-53 Rev. 4 IR-7 (1)

Incident Response

Automation Support For Availability Of Information / Support

Shared

n/a

IR-8

NIST_SP_800-53_R4_IR-8

NIST SP 800-53 Rev. 4 IR-8

Incident Response

Incident Response Plan

Shared

n/a

IR-4

NIST_SP_800-53_R5_IR-4

NIST SP 800-53 Rev. 5 IR-4

Incident Response

Incident Handling

Shared

n/a

a. Implement an incident handling capability for incidents that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradication, and recovery; b. Coordinate incident handling activities with contingency planning activities; c. Incorporate lessons learned from ongoing incident handling activities into incident response procedures, training, and testing, and implement the resulting changes accordingly; and d. Ensure the rigor, intensity, scope, and results of incident handling activities are comparable and predictable across the organization.

NIST_SP_800-53_R5_IR-4(1)

IR-4(1)

NIST SP 800-53 Rev. 5 IR-4 (1)

Incident Response

Automated Incident Handling Processes

Shared

n/a

Support the incident handling process using [Assignment: organization-defined automated mechanisms].

NIST_SP_800-53_R5_IR-4(4)

IR-4(4)

NIST SP 800-53 Rev. 5 IR-4 (4)

Incident Response

Information Correlation

Shared

n/a

Correlate incident information and individual incident responses to achieve an organization-wide perspective on incident awareness and response.

NIST_SP_800-53_R5_IR-7(1)

IR-7(1)

NIST SP 800-53 Rev. 5 IR-7 (1)

Incident Response

Automation Support for Availability of Information and Support

Shared

n/a

Increase the availability of incident response information and support using [Assignment: organization-defined automated mechanisms].

IR-8

NIST_SP_800-53_R5_IR-8

NIST SP 800-53 Rev. 5 IR-8

Incident Response

Incident Response Plan

Shared

n/a

a. Develop an incident response plan that: 1. Provides the organization with a roadmap for implementing its incident response capability; 2. Describes the structure and organization of the incident response capability; 3. Provides a high-level approach for how the incident response capability fits into the overall organization; 4. Meets the unique requirements of the organization, which relate to mission, size, structure, and functions; 5. Defines reportable incidents; 6. Provides metrics for measuring the incident response capability within the organization; 7. Defines the resources and management support needed to effectively maintain and mature an incident response capability; 8. Addresses the sharing of incident information; 9. Is reviewed and approved by [Assignment: organization-defined personnel or roles] [Assignment: organization-defined frequency]; and 10. Explicitly designates responsibility for incident response to [Assignment: organization-defined entities, personnel, or roles]. b. Distribute copies of the incident response plan to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; c. Update the incident response plan to address system and organizational changes or problems encountered during plan implementation, execution, or testing; d. Communicate incident response plan changes to [Assignment: organization-defined incident response personnel (identified by name and/or by role) and organizational elements]; and e. Protect the incident response plan from unauthorized disclosure and modification.

PCI_DSS_v4.0

12.10.2

PCI_DSS_v4.0_12.10.2

PCI DSS v4.0 12.10.2

Requirement 12: Support Information Security with Organizational Policies and Programs

Suspected and confirmed security incidents that could impact the CDE are responded to immediately

Shared

n/a

At least once every 12 months, the security incident response plan is: • Reviewed and the content is updated as needed. • Tested, including all elements listed in Requirement 12.10.1.

PCI_DSS_v4.0

12.10.5

PCI_DSS_v4.0_12.10.5

PCI DSS v4.0 12.10.5

Requirement 12: Support Information Security with Organizational Policies and Programs

Suspected and confirmed security incidents that could impact the CDE are responded to immediately

Shared

n/a

The security incident response plan includes monitoring and responding to alerts from security monitoring systems, including but not limited to: • Intrusion-detection and intrusion-prevention systems. • Network security controls. • Change-detection mechanisms for critical files. • The change-and tamper-detection mechanism for payment pages. This bullet is a best practice until its effective date; refer to Applicability Notes below for details. • Detection of unauthorized wireless access points.

PCI_DSS_v4.0

12.10.7

PCI_DSS_v4.0_12.10.7

PCI DSS v4.0 12.10.7

Requirement 12: Support Information Security with Organizational Policies and Programs

Suspected and confirmed security incidents that could impact the CDE are responded to immediately

Shared

n/a

Incident response procedures are in place, to be initiated upon the detection of stored PAN anywhere it is not expected, and include: • Determining what to do if PAN is discovered outside the CDE, including its retrieval, secure deletion, and/or migration into the currently defined CDE, as applicable. • Identifying whether sensitive authentication data is stored with PAN. • Determining where the account data came from and how it ended up where it was not expected. • Remediating data leaks or process gaps that resulted in the account data being where it was not expected.

SOC_2

CC7.4

SOC_2_CC7.4

SOC 2 Type 2 CC7.4

System Operations

Security incidents response

Shared

The customer is responsible for implementing this recommendation.

Assigns Roles and Responsibilities — Roles and responsibilities for the design, implementation, maintenance, and execution of the incident response program are assigned, including the use of external resources when necessary. • Contains Security Incidents — Procedures are in place to contain security incidents that actively threaten entity objectives. • Mitigates Ongoing Security Incidents — Procedures are in place to mitigate the effects of ongoing security incidents. • Ends Threats Posed by Security Incidents — Procedures are in place to end the threats posed by security incidents through closure of the vulnerability, removal of unauthorized access, and other remediation actions. • Restores Operations — Procedures are in place to restore data and business operations to an interim state that permits the achievement of entity objectives. • Develops and Implements Communication Protocols for Security Incidents — Protocols for communicating security incidents and actions taken to affected parties are developed and implemented to meet the entity's objectives. • Obtains Understanding of Nature of Incident and Determines Containment Strategy — An understanding of the nature (for example, the method by which the incident occurred and the affected system resources) and severity of the security incident is obtained to determine the appropriate containment strategy, including (1) a determination of the appropriate response time frame, and (2) the determination and execution of the containment approach. • Remediates Identified Vulnerabilities — Identified vulnerabilities are remediated through the development and execution of remediation activities. • Communicates Remediation Activities — Remediation activities are documented and communicated in accordance with the incident-response program. • Evaluates the Effectiveness of Incident Response — The design of incident-response activities is evaluated for effectiveness on a periodic basis. • Periodically Evaluates Incidents — Periodically, management reviews incidents related to security, availability, processing integrity, confidentiality, and privacy and identifies the need for system changes based on incident patterns and root causes Communicates Unauthorized Use and Disclosure — Events that resulted in unauthorized use or disclosure of personal information are communicated to the data subjects, legal and regulatory authorities, and others as required. • Application of Sanctions — The conduct of individuals and organizations operating under the authority of the entity and involved in the unauthorized use or disclosure of personal information is evaluated and, if appropriate, sanctioned in accordance with entity policies and legal and regulatory requirements

SOC_2

CC7.5

SOC_2_CC7.5

SOC 2 Type 2 CC7.5

System Operations

Recovery from identified security incidents

Shared

The customer is responsible for implementing this recommendation.

• Restores the Affected Environment — The activities restore the affected environment to functional operation by rebuilding systems, updating software, installing patches, and changing configurations, as needed. • Communicates Information About the Event — Communications about the nature of the incident, recovery actions taken, and activities required for the prevention of future security events are made to management and others as appropriate (internal and external). • Determines Root Cause of the Event — The root cause of the event is determined. • Implements Changes to Prevent and Detect Recurrences — Additional architecture or changes to preventive and detective controls, or both, are implemented to prevent and detect recurrences on a timely basis. • Improves Response and Recovery Procedures — Lessons learned are analyzed and the incident-response plan and recovery procedures are improved. • Implements Incident-Recovery Plan Testing — Incident-recovery plan testing is performed on a periodic basis. The testing includes (1) development of testing scenarios based on threat likelihood and magnitude; (2) consideration of relevant system components from across the entity that can impair availability; (3) scenarios that consider the potential for the lack of availability of key personnel; and (4) revision of continuity plans and systems based on test results

SWIFT_CSCF_v2022

11.2

SWIFT_CSCF_v2022_11.2

SWIFT CSCF v2022 11.2

11. Monitor in case of Major Disaster

Ensure a consistent and effective approach for the management of incidents (Problem Management).

Shared

n/a

Ensure a consistent and effective approach for the management of incidents (Problem Management).