Az Policy Advertizer

Azure_Security_Benchmark_v2.0

DP-5

Azure_Security_Benchmark_v2.0_DP-5

Azure Security Benchmark DP-5

Data Protection

Encrypt sensitive data at rest

Shared

To complement access controls, data at rest should be protected against ‘out of band’ attacks (such as accessing underlying storage) using encryption. This helps ensure that attackers cannot easily read or modify the data. Azure provides encryption for data at rest by default. For highly sensitive data, you have options to implement additional encryption at rest on all Azure resources where available. Azure manages your encryption keys by default, but Azure provides options to manage your own keys (customer managed keys) for certain Azure services. Understand encryption at rest in Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-atrest#encryption-at-rest-in-microsoft-cloud-services How to configure customer managed encryption keys: https://docs.microsoft.com/azure/storage/common/storage-encryption-keys-portal Encryption model and key management table: https://docs.microsoft.com/azure/security/fundamentals/encryption-models Data at rest double encryption in Azure: https://docs.microsoft.com/azure/security/fundamentals/double-encryption#data-at-rest

n/a

Azure_Security_Benchmark_v3.0

DP-4

Azure_Security_Benchmark_v3.0_DP-4

Microsoft cloud security benchmark DP-4

Data Protection

Enable data at rest encryption by default

Shared

**Security Principle:** To complement access controls, data at rest should be protected against 'out of band' attacks (such as accessing underlying storage) using encryption. This helps ensure that attackers cannot easily read or modify the data. **Azure Guidance:** Many Azure services have data at rest encryption enabled by default at the infrastructure layer using a service-managed key. Where technically feasible and not enabled by default, you can enable data at rest encryption in the Azure services, or in your VMs for storage level, file level, or database level encryption. **Implementation and additional context:** Understand encryption at rest in Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-atrest#encryption-at-rest-in-microsoft-cloud-services Data at rest double encryption in Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-models Encryption model and key management table: https://docs.microsoft.com/azure/security/fundamentals/encryption-models

n/a

CMMC_2.0_L2_SC.L2-3.13.16

CMMC_2.0_L2

SC.L2-3.13.16

404 not found

n/a

CMMC_L3

SC.3.177

CMMC_L3_SC.3.177

CMMC L3 SC.3.177

System and Communications Protection

Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.

Shared

Microsoft and the customer share responsibilities for implementing this requirement.

Cryptography can be employed to support many security solutions including the protection of controlled unclassified information, the provision of digital signatures, and the enforcement of information separation when authorized individuals have the necessary clearances for such information but lack the necessary formal access approvals. Cryptography can also be used to support random number generation and hash generation. Cryptographic standards include FIPSvalidated cryptography and/or NSA-approved cryptography.

CMMC_L3

SC.3.191

CMMC_L3_SC.3.191

CMMC L3 SC.3.191

System and Communications Protection

Protect the confidentiality of CUI at rest.

Shared

Microsoft and the customer share responsibilities for implementing this requirement.

Information at rest refers to the state of information when it is not in process or in transit and is located on storage devices as specific components of systems. The focus of protection at rest is not on the type of storage device or the frequency of access but rather the state of the information. Organizations can use different mechanisms to achieve confidentiality protections, including the use of cryptographic mechanisms and file share scanning. Organizations may also use other controls including secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved or continuous monitoring to identify malicious code at rest.

EU_GDPR_2016_679_Art._24

EU General Data Protection Regulation (GDPR) 2016/679 Art. 24

Chapter 4 - Controller and processor

Responsibility of the controller

Shared

n/a

306

EU_GDPR_2016_679_Art._25

EU General Data Protection Regulation (GDPR) 2016/679 Art. 25

Chapter 4 - Controller and processor

Data protection by design and by default

Shared

n/a

306

EU_GDPR_2016_679_Art._28

EU General Data Protection Regulation (GDPR) 2016/679 Art. 28

Chapter 4 - Controller and processor

Processor

Shared

n/a

306

EU_GDPR_2016_679_Art._32

EU General Data Protection Regulation (GDPR) 2016/679 Art. 32

Chapter 4 - Controller and processor

Security of processing

Shared

n/a

306

FedRAMP_High_R4

SC-28

FedRAMP_High_R4_SC-28

FedRAMP High SC-28

System And Communications Protection

Protection Of Information At Rest

Shared

n/a

The information system protects the [Selection (one or more): confidentiality; integrity] of [Assignment: organization-defined information at rest]. Supplemental Guidance: This control addresses the confidentiality and integrity of information at rest and covers user information and system information. Information at rest refers to the state of information when it is located on storage devices as specific components of information systems. System-related information requiring protection includes, for example, configurations or rule sets for firewalls, gateways, intrusion detection/prevention systems, filtering routers, and authenticator content. Organizations may employ different mechanisms to achieve confidentiality and integrity protections, including the use of cryptographic mechanisms and file share scanning. Integrity protection can be achieved, for example, by implementing Write-Once-Read-Many (WORM) technologies. Organizations may also employ other security controls including, for example, secure off-line storage in lieu of online storage when adequate protection of information at rest cannot otherwise be achieved and/or continuous monitoring to identify malicious code at rest. Related controls: AC-3, AC-6, CA-7, CM-3, CM-5, CM-6, PE-3, SC-8, SC-13, SI-3, SI-7. References: NIST Special Publications 800-56, 800-57, 800-111.

FedRAMP_High_R4

SC-28(1)

FedRAMP_High_R4_SC-28(1)

FedRAMP High SC-28 (1)

System And Communications Protection

Cryptographic Protection

Shared

n/a

The information system implements cryptographic mechanisms to prevent unauthorized disclosure and modification of [Assignment: organization-defined information] on [Assignment: organization-defined information system components]. Supplemental Guidance: Selection of cryptographic mechanisms is based on the need to protect the confidentiality and integrity of organizational information. The strength of mechanism is commensurate with the security category and/or classification of the information. This control enhancement applies to significant concentrations of digital media in organizational areas designated for media storage and also to limited quantities of media generally associated with information system components in operational environments (e.g., portable storage devices, mobile devices). Organizations have the flexibility to either encrypt all information on storage devices (i.e., full disk encryption) or encrypt specific data structures (e.g., files, records, or fields). Organizations employing cryptographic mechanisms to protect information at rest also consider cryptographic key management solutions. Related controls: AC-19, SC-12.

FedRAMP_Moderate_R4_SC-28

FedRAMP_Moderate_R4

SC-28

FedRAMP Moderate SC-28

System And Communications Protection

Protection Of Information At Rest

Shared

n/a

FedRAMP_Moderate_R4_SC-28(1)

FedRAMP_Moderate_R4

SC-28(1)

FedRAMP Moderate SC-28 (1)

System And Communications Protection

Cryptographic Protection

Shared

n/a

ISO27001-2013

A.10.1.1

ISO27001-2013_A.10.1.1

ISO 27001:2013 A.10.1.1

Cryptography

Policy on the use of cryptographic controls

Shared

n/a

A policy on the use of cryptographic controls for protection of information shall be developed and implemented.

2.10.1

K_ISMS_P_2018_2.10.1

K ISMS P 2018 2.10.1

2.10

Establish Procedures for Managing the Security of System Operations

Shared

n/a

Establish and implement operating procedures for managing the security of system operations such as designating system administrators, updating policies, changing rulesets, monitoring events, managing policy implementations or exceptions.

408

2.10.2

K_ISMS_P_2018_2.10.2

K ISMS P 2018 2.10.2

2.10

Establish Protective Measures for Administrator Privileges and Security Configurations

Shared

n/a

Establish and implement protective measures with regard to administrator privileges and security configurations to ensure that important information and personal information are not exposed as a result of unauthorized access by service type or misconfigurations.

385

2.7.1b

K_ISMS_P_2018_2.7.1b

K ISMS P 2018 2.7.1b

2.7

Ensure Data is Encrypted at Rest and In-Transit

Shared

n/a

Ensure data is encrypted when storing and transmitting personal and important information.

New_Zealand_ISM_23.4.9.C.01

3.4.3

K_ISMS_P_2018_3.4.3

K ISMS P 2018 3.4.3

3.4

Implement Measure to Protect the Personal Information of Dormant Users

Shared

n/a

Implement measures to protect the personal information of dormant users including notification of relevant matters, or disposal of storage of personal information.

mp.com.3 Protection of integrity and authenticity

404 not found

n/a

New_Zealand_ISM

23.4.9.C.01

23. Public Cloud Security

23.4.9.C.01 Data protection mechanisms

n/a

For each cloud service, agencies MUST ensure that the mechanisms used to protect data meet agency requirements.

NIS2

DP._Data_Protection_8

NIS2_DP._Data_Protection_8

DP. Data Protection

Policies and procedures regarding the use of cryptography and, where appropriate, encryption

n/a

In order to safeguard the security of public electronic communications networks and publicly available electronic communications services, the use of encryption technologies, in particular end-to-end encryption as well as data-centric security concepts, such as cartography, segmentation, tagging, access policy and access management, and automated access decisions, should be promoted. Where necessary, the use of encryption, in particular end-to-end encryption should be mandatory for providers of public electronic communications networks or of publicly available electronic communications services in accordance with the principles of security and privacy by default and by design for the purposes of this Directive. The use of end-to-end encryption should be reconciled with the Member States’ powers to ensure the protection of their essential security interests and public security, and to allow for the prevention, investigation, detection and prosecution of criminal offences in accordance with Union law. However, this should not weaken end-to-end encryption, which is a critical technology for the effective protection of data and privacy and the security of communications.

NIST_SP_800-171_R2_3

.13.16

NIST_SP_800-171_R2_3.13.16

NIST SP 800-171 R2 3.13.16

System and Communications Protection

Protect the confidentiality of CUI at rest.

Shared

Microsoft and the customer share responsibilities for implementing this requirement.

NIST_SP_800-53_R4

SC-28

NIST_SP_800-53_R4_SC-28

NIST SP 800-53 Rev. 4 SC-28

System And Communications Protection

Protection Of Information At Rest

Shared

n/a

NIST_SP_800-53_R4_SC-28(1)

NIST_SP_800-53_R4

SC-28(1)

NIST SP 800-53 Rev. 4 SC-28 (1)

System And Communications Protection

Cryptographic Protection

Shared

n/a

NIST_SP_800-53_R5

SC-28

NIST_SP_800-53_R5_SC-28

NIST SP 800-53 Rev. 5 SC-28

System and Communications Protection

Protection of Information at Rest

Shared

n/a

Protect the [Selection (OneOrMore): confidentiality;integrity] of the following information at rest: [Assignment: organization-defined information at rest].

NIST_SP_800-53_R5_SC-28(1)

NIST_SP_800-53_R5

SC-28(1)

NIST SP 800-53 Rev. 5 SC-28 (1)

System and Communications Protection

Cryptographic Protection

Shared

n/a

Implement cryptographic mechanisms to prevent unauthorized disclosure and modification of the following information at rest on [Assignment: organization-defined system components or media]: [Assignment: organization-defined information].

NZ_ISM_v3.5

CR-3

NZ_ISM_v3.5_CR-3

NZISM Security Benchmark CR-3

Cryptography

17.1.53 Reducing storage and physical transfer requirements

Customer

n/a

When encryption is applied to media or media residing within IT equipment it provides an additional layer of defence. Whilst such measures do not reduce or alter the classification of the information itself, physical storage, handling and transfer requirements may be reduced to those of a lesser classification for the media or equipment (but not the data itself).

op.acc.6 Authentication mechanism (organization users)

404 not found

n/a

PCI_DSS_V3.2.1

3.4

PCI_DSS_v3.2.1_3.4

PCI DSS v3.2.1 3.4

Requirement 3

PCI DSS requirement 3.4

customer

n/a

PCI_DSS_V3.2.1

4.1

PCI_DSS_v3.2.1_4.1

PCI DSS v3.2.1 4.1

Requirement 4

PCI DSS requirement 4.1

customer

n/a

PCI_DSS_V3.2.1

6.5.3

PCI_DSS_v3.2.1_6.5.3

PCI DSS v3.2.1 6.5.3

Requirement 6

PCI DSS requirement 6.5.3

shared

n/a

PCI_DSS_v4.0

3.5.1

PCI_DSS_v4.0_3.5.1

PCI DSS v4.0 3.5.1

Requirement 03: Protect Stored Account Data

Primary account number (PAN) is secured wherever it is stored

Shared

n/a

PAN is rendered unreadable anywhere it is stored by using any of the following approaches: • One-way hashes based on strong cryptography of the entire PAN. • Truncation (hashing cannot be used to replace the truncated segment of PAN). – If hashed and truncated versions of the same PAN, or different truncation formats of the same PAN, are present in an environment, additional controls are in place such that the different versions cannot be correlated to reconstruct the original PAN. • Index tokens. • Strong cryptography with associated keymanagement processes and procedures.

PCI_DSS_v4.0

6.2.4

PCI_DSS_v4.0_6.2.4

PCI DSS v4.0 6.2.4

Requirement 06: Develop and Maintain Secure Systems and Software

Bespoke and custom software are developed securely

Shared

n/a

Software engineering techniques or other methods are defined and in use for bespoke and custom software by software development personnel to prevent or mitigate common software attacks and related vulnerabilities, including but not limited to the following: • Injection attacks, including SQL, LDAP, XPath, or other command, parameter, object, fault, or injection-type flaws. • Attacks on data and data structures, including attempts to manipulate buffers, pointers, input data, or shared data. • Attacks on cryptography usage, including attempts to exploit weak, insecure, or inappropriate cryptographic implementations, algorithms, cipher suites, or modes of operation. • Attacks on business logic, including attempts to abuse or bypass application features and functionalities through the manipulation of APIs, communication protocols and channels, clientside functionality, or other system/application functions and resources. This includes cross-site scripting (XSS) and cross-site request forgery (CSRF). • Attacks on access control mechanisms, including attempts to bypass or abuse identification, authentication, or authorization mechanisms, or attempts to exploit weaknesses in the implementation of such mechanisms. • Attacks via any “high-risk” vulnerabilities identified in the vulnerability identification process, as defined in Requirement 6.3.1.

RBI_CSF_Banks_v2016

13.4

RBI_CSF_Banks_v2016_13.4

Advanced Real-Timethreat Defenceand Management

Advanced Real-Timethreat Defenceand Management-13.4

n/a

Consider implementingsecure web gateways with capability to deep scan network packets including secure (HTTPS, etc.) traffic passing through the web/internet gateway

RBI_ITF_NBFC_v2017

3.1.h

RBI_ITF_NBFC_v2017_3.1.h

RBI IT Framework 3.1.h

Information and Cyber Security

Public Key Infrastructure (PKI)-3.1

n/a

The IS Policy must provide for a IS framework with the following basic tenets: Public Key Infrastructure (PKI) - NBFCs may increase the usage of PKI to ensure confidentiality of data, access control, data integrity, authentication and nonrepudiation.

SOC_2

CC6.1

SOC_2_CC6.1

SOC 2 Type 2 CC6.1

Logical and Physical Access Controls

Logical access security software, infrastructure, and architectures

Shared

The customer is responsible for implementing this recommendation.

The following points of focus, specifically related to all engagements using the trust services criteria, highlight important characteristics relating to this criterion: • Identifies and Manages the Inventory of Information Assets — The entity identifies, Page 29 TSP Ref. # TRUST SERVICES CRITERIA AND POINTS OF FOCUS inventories, classifies, and manages information assets. • Restricts Logical Access — Logical access to information assets, including hardware, data (at-rest, during processing, or in transmission), software, administrative authorities, mobile devices, output, and offline system components is restricted through the use of access control software and rule sets. • Identifies and Authenticates Users — Persons, infrastructure, and software are identified and authenticated prior to accessing information assets, whether locally or remotely. • Considers Network Segmentation — Network segmentation permits unrelated portions of the entity's information system to be isolated from each other. • Manages Points of Access — Points of access by outside entities and the types of data that flow through the points of access are identified, inventoried, and managed. The types of individuals and systems using each point of access are identified, documented, and managed. • Restricts Access to Information Assets — Combinations of data classification, separate data structures, port restrictions, access protocol restrictions, user identification, and digital certificates are used to establish access-control rules for information assets. • Manages Identification and Authentication — Identification and authentication requirements are established, documented, and managed for individuals and systems accessing entity information, infrastructure, and software. • Manages Credentials for Infrastructure and Software — New internal and external infrastructure and software are registered, authorized, and documented prior to being granted access credentials and implemented on the network or access point. Credentials are removed and access is disabled when access is no longer required or the infrastructure and software are no longer in use. • Uses Encryption to Protect Data — The entity uses encryption to supplement other measures used to protect data at rest, when such protections are deemed appropriate based on assessed risk. • Protects Encryption Keys — Processes are in place to protect encryption keys during generation, storage, use, and destruction

SWIFT_CSCF_v2021

2.1

SWIFT_CSCF_v2021_2.1

SWIFT CSCF v2021 2.1

Reduce Attack Surface and Vulnerabilities

Internal Data Flow Security

n/a

Ensure the confidentiality, integrity, and authenticity of application data flows between local SWIFT-related applications.

SWIFT_CSCF_v2021

2.4A

SWIFT_CSCF_v2021_2.4A

SWIFT CSCF v2021 2.4A

Reduce Attack Surface and Vulnerabilities

Back-office Data Flow Security

n/a

Ensure the confidentiality, integrity, and mutual authenticity of data flows between local or remote SWIFT infrastructure components and the back office first hops they connect to.

SWIFT_CSCF_v2021

2.5A

SWIFT_CSCF_v2021_2.5A

SWIFT CSCF v2021 2.5A

Reduce Attack Surface and Vulnerabilities

External Transmission Data Protection

n/a

Protect the confidentiality of SWIFT-related data transmitted or stored outside of the secure zone as part of operational processes.

SWIFT_CSCF_v2022

2.1

SWIFT_CSCF_v2022_2.1

SWIFT CSCF v2022 2.1

2. Reduce Attack Surface and Vulnerabilities

Ensure the confidentiality, integrity, and authenticity of application data flows between local SWIFT-related components.

Shared

n/a

Confidentiality, integrity, and authentication mechanisms are implemented to protect SWIFT-related component-to-component or system-to-system data flows.

SWIFT_CSCF_v2022

2.4A

SWIFT_CSCF_v2022_2.4A

SWIFT CSCF v2022 2.4A

2. Reduce Attack Surface and Vulnerabilities

Back-office Data Flow Security

Customer

n/a

Ensure the confidentiality, integrity, and mutual authenticity of data flows between local or remote SWIFT infrastructure components and the back office first hops they connect to.

SWIFT_CSCF_v2022

2.5A

SWIFT_CSCF_v2022_2.5A

SWIFT CSCF v2022 2.5A

2. Reduce Attack Surface and Vulnerabilities

External Transmission Data Protection

Customer

n/a

Protect the confidentiality of SWIFT-related data transmitted or stored outside of the secure zone as part of operational processes.

U.07.3 - Management features

404 not found

n/a

U.11.1 - Policy

404 not found

n/a

U.11.2 - Cryptographic measures

404 not found

n/a

UK_NCSC_CSP

2.3

UK_NCSC_CSP_2.3

UK NCSC CSP 2.3

Asset protection and resilience

Data at rest protection

Shared

n/a

To ensure data is not available to unauthorised parties with physical access to infrastructure, user data held within the service should be protected regardless of the storage media on which it’s held. Without appropriate measures in place, data may be inadvertently disclosed on discarded, lost or stolen media.