Az Policy Advertizer

2.11

CIS_Azure_1.1.0_2.11

CIS Microsoft Azure Foundations Benchmark recommendation 2.11

2 Security Center

Ensure ASC Default policy setting "Monitor Storage Blob Encryption" is not "Disabled"

Shared

The customer is responsible for implementing this recommendation.

Enable storage encryption recommendations.

2.15

CIS_Azure_1.1.0_2.15

CIS Microsoft Azure Foundations Benchmark recommendation 2.15

2 Security Center

Ensure ASC Default policy setting "Monitor SQL Encryption" is not "Disabled"

Shared

The customer is responsible for implementing this recommendation.

Enable SQL encryption recommendations.

2.6

CIS_Azure_1.1.0_2.6

CIS Microsoft Azure Foundations Benchmark recommendation 2.6

2 Security Center

Ensure ASC Default policy setting "Monitor Disk Encryption" is not "Disabled"

Shared

The customer is responsible for implementing this recommendation.

Enable Disk encryption recommendations for virtual machines.

4.10

CIS_Azure_1.1.0_4.10

CIS Microsoft Azure Foundations Benchmark recommendation 4.10

4 Database Services

Ensure SQL server's TDE protector is encrypted with BYOK (Use your own key)

Shared

The customer is responsible for implementing this recommendation.

TDE with BYOK support provides increased transparency and control over the TDE Protector, increased security with an HSM-backed external service, and promotion of separation of duties. With TDE, data is encrypted at rest with a symmetric key (called the database encryption key) stored in the database or data warehouse distribution. To protect this data encryption key (DEK) in the past, only a certificate that the Azure SQL Service managed could be used. Now, with BYOK support for TDE, the DEK can be protected with an asymmetric key that is stored in the Key Vault. Key Vault is a highly available and scalable cloud-based key store which offers central key management, leverages FIPS 140-2 Level 2 validated hardware security modules (HSMs), and allows separation of management of keys and data, for additional security. Based on business needs or criticality of data/databases hosted a SQL server, it is recommended that the TDE protector is encrypted by a key that is managed by the data owner (BYOK).

4.9

CIS_Azure_1.1.0_4.9

CIS Microsoft Azure Foundations Benchmark recommendation 4.9

4 Database Services

Ensure that 'Data encryption' is set to 'On' on a SQL Database

Shared

The customer is responsible for implementing this recommendation.

Enable Transparent Data Encryption on every SQL server.

7.1

CIS_Azure_1.1.0_7.1

CIS Microsoft Azure Foundations Benchmark recommendation 7.1

7 Virtual Machines

Ensure that 'OS disk' are encrypted

Shared

The customer is responsible for implementing this recommendation.

Ensure that OS disks (boot volumes) are encrypted, where possible.

7.2

CIS_Azure_1.1.0_7.2

CIS Microsoft Azure Foundations Benchmark recommendation 7.2

7 Virtual Machines

Ensure that 'Data disks' are encrypted

Shared

The customer is responsible for implementing this recommendation.

Ensure that data disks (non-boot volumes) are encrypted, where possible.

7.3

CIS_Azure_1.1.0_7.3

CIS Microsoft Azure Foundations Benchmark recommendation 7.3

7 Virtual Machines

Ensure that 'Unattached disks' are encrypted

Shared

The customer is responsible for implementing this recommendation.

Ensure that unattached disks in a subscription are encrypted.

3.9

CIS_Azure_1.3.0_3.9

CIS Microsoft Azure Foundations Benchmark recommendation 3.9

3 Storage Accounts

Ensure storage for critical data are encrypted with Customer Managed Key

Shared

The customer is responsible for implementing this recommendation.

Enable sensitive data encryption at rest using Customer Managed Keys rather than Microsoft Managed keys

4.1.2

CIS_Azure_1.3.0_4.1.2

CIS Microsoft Azure Foundations Benchmark recommendation 4.1.2

4 Database Services

Ensure that 'Data encryption' is set to 'On' on a SQL Database

Shared

The customer is responsible for implementing this recommendation.

Enable Transparent Data Encryption on every SQL server.

4.5

CIS_Azure_1.3.0_4.5

CIS Microsoft Azure Foundations Benchmark recommendation 4.5

4 Database Services

Ensure SQL server's TDE protector is encrypted with Customer-managed key

Shared

The customer is responsible for implementing this recommendation.

TDE with Customer-managed key support provides increased transparency and control over the TDE Protector, increased security with an HSM-backed external service, and promotion of separation of duties. With TDE, data is encrypted at rest with a symmetric key (called the database encryption key) stored in the database or data warehouse distribution. To protect this data encryption key (DEK) in the past, only a certificate that the Azure SQL Service managed could be used. Now, with Customer-managed key support for TDE, the DEK can be protected with an asymmetric key that is stored in the Key Vault. Key Vault is a highly available and scalable cloud-based key store which offers central key management, leverages FIPS 140-2 Level 2 validated hardware security modules (HSMs), and allows separation of management of keys and data, for additional security. Based on business needs or criticality of data/databases hosted a SQL server, it is recommended that the TDE protector is encrypted by a key that is managed by the data owner (Customer-managed key).

7.2

CIS_Azure_1.3.0_7.2

CIS Microsoft Azure Foundations Benchmark recommendation 7.2

7 Virtual Machines

Ensure that 'OS and Data' disks are encrypted with CMK

Shared

The customer is responsible for implementing this recommendation.

Ensure that OS disks (boot volumes) and data disks (non-boot volumes) are encrypted with CMK.

7.3

CIS_Azure_1.3.0_7.3

CIS Microsoft Azure Foundations Benchmark recommendation 7.3

7 Virtual Machines

Ensure that 'Unattached disks' are encrypted with CMK

Shared

The customer is responsible for implementing this recommendation.

Ensure that unattached disks in a subscription are encrypted with a Customer Managed Key (CMK).

7.7

CIS_Azure_1.3.0_7.7

CIS Microsoft Azure Foundations Benchmark recommendation 7.7

7 Virtual Machines

Ensure that VHD's are encrypted

Shared

The customer is responsible for implementing this recommendation.

VHD (Virtual Hard Disks) are stored in BLOB storage and are the old style disks that were attached to Virtual Machines, and the BLOB VHD was then leased to the VM. By Default storage accounts are not encrypted, and Azure Defender(Security Centre) would then recommend that the OS disks should be encrypted. Storage accounts can be encrypted as a whole using PMK or CMK and this should be turned on for storage accounts containing VHD's.

3.9

CIS_Azure_1.4.0_3.9

CIS Microsoft Azure Foundations Benchmark recommendation 3.9

3 Storage Accounts

Ensure Storage for Critical Data are Encrypted with Customer Managed Keys

Shared

The customer is responsible for implementing this recommendation.

Enable sensitive data encryption at rest using Customer Managed Keys rather than Microsoft Managed keys

4.1.2

CIS_Azure_1.4.0_4.1.2

CIS Microsoft Azure Foundations Benchmark recommendation 4.1.2

4 Database Services

Ensure that 'Data encryption' is set to 'On' on a SQL Database

Shared

The customer is responsible for implementing this recommendation.

Enable Transparent Data Encryption on every SQL server.

4.3.8

CIS_Azure_1.4.0_4.3.8

CIS Microsoft Azure Foundations Benchmark recommendation 4.3.8

4 Database Services

Ensure 'Infrastructure double encryption' for PostgreSQL Database Server is 'Enabled'

Shared

The customer is responsible for implementing this recommendation.

Enable encryption at rest for PostgreSQL Databases.

4.6

CIS_Azure_1.4.0_4.6

CIS Microsoft Azure Foundations Benchmark recommendation 4.6

4 Database Services

Ensure SQL server's TDE protector is encrypted with Customer-managed key

Shared

The customer is responsible for implementing this recommendation.

7.2

CIS_Azure_1.4.0_7.2

CIS Microsoft Azure Foundations Benchmark recommendation 7.2

7 Virtual Machines

Ensure that 'OS and Data' disks are encrypted with Customer Managed Key (CMK)

Shared

The customer is responsible for implementing this recommendation.

Ensure that OS disks (boot volumes) and data disks (non-boot volumes) are encrypted with CMK (Customer Managed Keys). Customer Managed keys can be either ADE or Server Side Encryption(SSE)

7.3

CIS_Azure_1.4.0_7.3

CIS Microsoft Azure Foundations Benchmark recommendation 7.3

7 Virtual Machines

Ensure that 'Unattached disks' are encrypted with CMK

Shared

The customer is responsible for implementing this recommendation.

Ensure that unattached disks in a subscription are encrypted with a Customer Managed Key (CMK).

7.7

CIS_Azure_1.4.0_7.7

CIS Microsoft Azure Foundations Benchmark recommendation 7.7

7 Virtual Machines

Ensure that VHD's are Encrypted

Shared

The customer is responsible for implementing this recommendation.

3.12

CIS_Azure_2.0.0_3.12

CIS Microsoft Azure Foundations Benchmark recommendation 3.12

Ensure Storage for Critical Data are Encrypted with Customer Managed Keys

Shared

If the key expires by setting the 'activation date' and 'expiration date', the user must rotate the key manually. Using Customer Managed Keys may also incur additional man-hour requirements to create, store, manage, and protect the keys as needed.

Enable sensitive data encryption at rest using Customer Managed Keys rather than Microsoft Managed keys. By default, data in the storage account is encrypted using Microsoft Managed Keys at rest. All Azure Storage resources are encrypted, including blobs, disks, files, queues, and tables. All object metadata is also encrypted. If you want to control and manage this encryption key yourself, however, you can specify a customer-managed key. That key is used to protect and control access to the key that encrypts your data. You can also choose to automatically update the key version used for Azure Storage encryption whenever a new version is available in the associated Key Vault.

4.1.3

CIS_Azure_2.0.0_4.1.3

CIS Microsoft Azure Foundations Benchmark recommendation 4.1.3

4.1

Ensure SQL server's Transparent Data Encryption (TDE) protector is encrypted with Customer-managed key

Shared

Once TDE protector is encrypted with a Customer-managed key, it transfers entire responsibility of respective key management on to you, and hence you should be more careful about doing any operations on the particular key in order to keep data from corresponding SQL server and Databases hosted accessible. When deploying Customer Managed Keys, it is prudent to ensure that you also deploy an automated toolset for managing these keys (this should include discovery and key rotation), and Keys should be stored in an HSM or hardware backed keystore, such as Azure Key Vault. As far as toolsets go, check with your cryptographic key provider, as they may well provide one as an add-on to their service.

Transparent Data Encryption (TDE) with Customer-managed key support provides increased transparency and control over the TDE Protector, increased security with an HSM-backed external service, and promotion of separation of duties. With TDE, data is encrypted at rest with a symmetric key (called the database encryption key) stored in the database or data warehouse distribution. To protect this data encryption key (DEK) in the past, only a certificate that the Azure SQL Service managed could be used. Now, with Customer-managed key support for TDE, the DEK can be protected with an asymmetric key that is stored in the Azure Key Vault. The Azure Key Vault is a highly available and scalable cloud-based key store which offers central key management, leverages FIPS 140-2 Level 2 validated hardware security modules (HSMs), and allows separation of management of keys and data for additional security. Based on business needs or criticality of data/databases hosted on a SQL server, it is recommended that the TDE protector is encrypted by a key that is managed by the data owner (Customer-managed key). Customer-managed key support for Transparent Data Encryption (TDE) allows user control of TDE encryption keys and restricts who can access them and when. Azure Key Vault, Azure’s cloud-based external key management system, is the first key management service where TDE has integrated support for Customer-managed keys. With Customer-managed key support, the database encryption key is protected by an asymmetric key stored in the Key Vault. The asymmetric key is set at the server level and inherited by all databases under that server.

4.1.5

CIS_Azure_2.0.0_4.1.5

CIS Microsoft Azure Foundations Benchmark recommendation 4.1.5

4.1

Ensure that 'Data encryption' is set to 'On' on a SQL Database

Shared

n/a

Enable Transparent Data Encryption on every SQL server. Azure SQL Database transparent data encryption helps protect against the threat of malicious activity by performing real-time encryption and decryption of the database, associated backups, and transaction log files at rest without requiring changes to the application.

4.3.8

CIS_Azure_2.0.0_4.3.8

CIS Microsoft Azure Foundations Benchmark recommendation 4.3.8

4.3

Ensure 'Infrastructure double encryption' for PostgreSQL Database Server is 'Enabled'

Shared

The read and write speeds to the database will be impacted if both default encryption and Infrastructure Encryption are checked, as a secondary form of encryption requires more resource overhead for the cryptography of information. This cost is justified for information security. Customer managed keys are recommended for the most secure implementation, leading to overhead of key management. The key will also need to be backed up in a secure location, as loss of the key will mean loss of the information in the database.

Azure Database for PostgreSQL servers should be created with 'infrastructure double encryption' enabled. If Double Encryption is enabled, another layer of encryption is implemented at the hardware level before the storage or network level. Information will be encrypted before it is even accessed, preventing both interception of data in motion if the network layer encryption is broken and data at rest in system resources such as memory or processor cache. Encryption will also be in place for any backups taken of the database, so the key will secure access the data in all forms. For the most secure implementation of key based encryption, it is recommended to use a Customer Managed asymmetric RSA 2048 Key in Azure Key Vault.

7.3

CIS_Azure_2.0.0_7.3

CIS Microsoft Azure Foundations Benchmark recommendation 7.3

Ensure that 'OS and Data' disks are encrypted with Customer Managed Key (CMK)

Shared

Using CMK/BYOK will entail additional management of keys. **NOTE:** You must have your key vault set up to utilize this.

Ensure that OS disks (boot volumes) and data disks (non-boot volumes) are encrypted with CMK (Customer Managed Keys). Customer Managed keys can be either ADE or Server Side Encryption (SSE). Encrypting the IaaS VM's OS disk (boot volume) and Data disks (non-boot volume) ensures that the entire content is fully unrecoverable without a key, thus protecting the volume from unwanted reads. PMK (Platform Managed Keys) are enabled by default in Azure-managed disks and allow encryption at rest. CMK is recommended because it gives the customer the option to control which specific keys are used for the encryption and decryption of the disk. The customer can then change keys and increase security by disabling them instead of relying on the PMK key that remains unchanging. There is also the option to increase security further by using automatically rotating keys so that access to disk is ensured to be limited. Organizations should evaluate what their security requirements are, however, for the data stored on the disk. For high-risk data using CMK is a must, as it provides extra steps of security. If the data is low risk, PMK is enabled by default and provides sufficient data security.

7.4

CIS_Azure_2.0.0_7.4

CIS Microsoft Azure Foundations Benchmark recommendation 7.4

Ensure that 'Unattached disks' are encrypted with 'Customer Managed Key' (CMK)

Shared

**NOTE:** You must have your key vault set up to utilize this. Encryption is available only on Standard tier VMs. This might cost you more. Utilizing and maintaining Customer-managed keys will require additional work to create, protect, and rotate keys.

Ensure that unattached disks in a subscription are encrypted with a Customer Managed Key (CMK). Managed disks are encrypted by default with Platform-managed keys. Using Customer-managed keys may provide an additional level of security or meet an organization's regulatory requirements. Encrypting managed disks ensures that its entire content is fully unrecoverable without a key and thus protects the volume from unwarranted reads. Even if the disk is not attached to any of the VMs, there is always a risk where a compromised user account with administrative access to VM service can mount/attach these data disks, which may lead to sensitive information disclosure and tampering.

7.7

CIS_Azure_2.0.0_7.7

CIS Microsoft Azure Foundations Benchmark recommendation 7.7

[Legacy] Ensure that VHDs are Encrypted

Shared

Depending on how the encryption is implemented will change the size of the impact. If provider-managed keys(PMK) are utilized, the impact is relatively low, but processes need to be put in place to regularly rotate the keys. If Customer-managed keys(CMK) are utilized, a key management process needs to be implemented to store and manage key rotation, thus the impact is medium to high depending on user maturity with key management.

**NOTE: This is a legacy recommendation. Managed Disks are encrypted by default and recommended for all new VM implementations.** VHD (Virtual Hard Disks) are stored in blob storage and are the old-style disks that were attached to Virtual Machines. The blob VHD was then leased to the VM. By default, storage accounts are not encrypted, and Microsoft Defender will then recommend that the OS disks should be encrypted. Storage accounts can be encrypted as a whole using PMK or CMK. This should be turned on for storage accounts containing VHDs. While it is recommended to use Managed Disks which are encrypted by default, "legacy" VHDs may exist for a variety of reasons and may need to remain in VHD format. VHDs are not encrypted by default, so this recommendation intends to address the security of these disks. In these niche cases, VHDs should be encrypted using the procedures in this recommendation to encrypt and protect the data content. If a virtual machine is using a VHD and can be converted to a managed disk, instructions for this procedure can be found in the resources section of this recommendation under the title "Convert VHD to Managed Disk."

FedRAMP_High_R4

PS-3(3)

FedRAMP_High_R4_PS-3(3)

FedRAMP High PS-3 (3)

Personnel Security

Information With Special Protection Measures

Shared

n/a

The organization ensures that individuals accessing an information system processing, storing, or transmitting information requiring special protection: (a) Have valid access authorizations that are demonstrated by assigned official government duties; and (b) Satisfy [Assignment: organization-defined additional personnel screening criteria]. Supplemental Guidance: Organizational information requiring special protection includes, for example, Controlled Unclassified Information (CUI) and Sources and Methods Information (SAMI). Personnel security criteria include, for example, position sensitivity background screening requirements.

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_Moderate_R4_PS-3(3)

FedRAMP_Moderate_R4

PS-3(3)

FedRAMP Moderate PS-3 (3)

Personnel Security

Information With Special Protection Measures

Shared

n/a

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

hipaa-0105.02a2Organizational.1-02.a

0105.02a2Organizational.1-02.a

0105.02a2Organizational.1-02.a

01 Information Protection Program

0105.02a2Organizational.1-02.a 02.01 Prior to Employment

Shared

n/a

Risk designations are assigned for all positions within the organization as appropriate, with commensurate screening criteria, and reviewed/revised every 365 days.

hipaa-0106.02a2Organizational.23-02.a

0106.02a2Organizational.23-02.a

0106.02a2Organizational.23-02.a

01 Information Protection Program

0106.02a2Organizational.23-02.a 02.01 Prior to Employment

Shared

n/a

The pre-employment process is reviewed by recruitment to ensure security roles/responsibilities are specifically defined (in writing) and clearly communicated to job candidates.

hipaa-0901.09s1Organizational.1-09.s

0901.09s1Organizational.1-09.s

0901.09s1Organizational.1-09.s

09 Transmission Protection

0901.09s1Organizational.1-09.s 09.08 Exchange of Information

Shared

n/a

The organization formally addresses multiple safeguards before allowing the use of information systems for information exchange.

hipaa-0947.09y2Organizational.2-09.y

0947.09y2Organizational.2-09.y

0947.09y2Organizational.2-09.y

09 Transmission Protection

0947.09y2Organizational.2-09.y 09.09 Electronic Commerce Services

Shared

n/a

The organization ensures the storage of the transaction details are located outside of any publicly accessible environments (e.g., on a storage platform existing on the organization's intranet) and not retained and exposed on a storage medium directly accessible from the Internet.

hipaa-1008.01d2System.3-01.d

1008.01d2System.3-01.d

1008.01d2System.3-01.d

10 Password Management

1008.01d2System.3-01.d 01.02 Authorized Access to Information Systems

Shared

n/a

Users sign a statement acknowledging their responsibility to keep passwords confidential.

hipaa-1132.01v2System.3-01.v

1132.01v2System.3-01.v

1132.01v2System.3-01.v

11 Access Control

1132.01v2System.3-01.v 01.06 Application and Information Access Control

Shared

n/a

Covered information is encrypted when stored in non-secure areas and, if not encrypted at rest, the organization documents its rationale.

hipaa-1134.01v3System.1-01.v

1134.01v3System.1-01.v

1134.01v3System.1-01.v

11 Access Control

1134.01v3System.1-01.v 01.06 Application and Information Access Control

Shared

n/a

Copy, move, print, and storage of sensitive data are prohibited when accessed remotely without a defined business need.

hipaa-1903.06d1Organizational.3456711-06.d

1903.06d1Organizational.3456711-06.d

1903.06d1Organizational.3456711-06.d

19 Data Protection & Privacy

1903.06d1Organizational.3456711-06.d 06.01 Compliance with Legal Requirements

Shared

n/a

The confidentiality and integrity of covered information at rest is protected using an encryption method appropriate to the medium where it is stored; where the organization chooses not to encrypt covered information, a documented rationale for not doing so is maintained or alternative compensating controls are used if the method is approved and reviewed annually by the CISO.

ISO27001-2013

A.8.2.3

ISO27001-2013_A.8.2.3

ISO 27001:2013 A.8.2.3

Asset Management

Handling of assets

Shared

n/a

Procedures for handling assets shall be developed and implemented in accordance with the information classification scheme adopted by the organization.

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.

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. See [NIST CRYPTO].

NIST_SP_800-53_R4_PS-3(3)

NIST_SP_800-53_R4

PS-3(3)

NIST SP 800-53 Rev. 4 PS-3 (3)

Personnel Security

Information With Special Protection Measures

Shared

n/a

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_R5_PS-3(3)

NIST_SP_800-53_R5

PS-3(3)

NIST SP 800-53 Rev. 5 PS-3 (3)

Personnel Security

Information Requiring Special Protective Measures

Shared

n/a

Verify that individuals accessing a system processing, storing, or transmitting information requiring special protection: (a) Have valid access authorizations that are demonstrated by assigned official government duties; and (b) Satisfy [Assignment: organization-defined additional personnel screening criteria].

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].

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.

3.5.1.1

PCI_DSS_v4.0_3.5.1.1

PCI DSS v4.0 3.5.1.1

Requirement 03: Protect Stored Account Data

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

Shared

n/a

Hashes used to render PAN unreadable (per the first bullet of Requirement 3.5.1) are keyed cryptographic hashes of the entire PAN, with associated key-management processes and procedures in accordance with Requirements 3.6 and 3.7.

3.5.1.2

PCI_DSS_v4.0_3.5.1.2

PCI DSS v4.0 3.5.1.2

Requirement 03: Protect Stored Account Data

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

Shared

n/a

If disk-level or partition-level encryption (rather than file-, column-, or field-level database encryption) is used to render PAN unreadable, it is implemented only as follows: • On removable electronic media, OR • If used for non-removable electronic media, PAN is also rendered unreadable via another mechanism that meets Requirement 3.5.1.

3.5.1.3

PCI_DSS_v4.0_3.5.1.3

PCI DSS v4.0 3.5.1.3

Requirement 03: Protect Stored Account Data

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

Shared

n/a

If disk-level or partition-level encryption is used (rather than file-, column-, or field--level database encryption) to render PAN unreadable, it is managed as follows: • Logical access is managed separately and independently of native operating system authentication and access control mechanisms. • Decryption keys are not associated with user accounts.

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_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

5.3A

SWIFT_CSCF_v2022_5.3A

SWIFT CSCF v2022 5.3A

5. Manage Identities and Segregate Privileges

To the extent permitted and practicable, ensure the trustworthiness of staff operating the local SWIFT environment by performing regular staff screening.

Shared

n/a

Staff operating the local SWIFT infrastructure are screened prior to initial appointment in that role and periodically thereafter.