Revoke privileged roles as appropriate - 32f22cfa-770b-057c-965b-450898425519

All Global Administrators will receive a notification from Azure every time a password is reset. This is useful for auditing procedures to confirm that there are no out of the ordinary password resets for Global Administrators. There is additional overhead, however, in the time required for Global Administrators to audit the notifications. This setting is only useful if all Global Administrators pay attention to the notifications, and audit each one.

Ensure that all Global Administrators are notified if any other administrator resets their password. Global Administrator accounts are sensitive. Any password reset activity notification, when sent to all Global Administrators, ensures that all Global administrators can passively confirm if such a reset is a common pattern within their group. For example, if all Global Administrators change their password every 30 days, any password reset activity before that may require administrator(s) to evaluate any unusual activity and confirm its origin.

link

CIS_Azure_2.0.0

3.6

CIS_Azure_2.0.0_3.6

CIS Microsoft Azure Foundations Benchmark recommendation 3.6

Ensure that Shared Access Signature Tokens Expire Within an Hour

Shared

n/a

Expire shared access signature tokens within an hour. A shared access signature (SAS) is a URI that grants restricted access rights to Azure Storage resources. A shared access signature can be provided to clients who should not be trusted with the storage account key but for whom it may be necessary to delegate access to certain storage account resources. Providing a shared access signature URI to these clients allows them access to a resource for a specified period of time. This time should be set as low as possible and preferably no longer than an hour.

link

FedRAMP_High_R4

AC-2(3)

FedRAMP_High_R4_AC-2(3)

FedRAMP High AC-2 (3)

Access Control

Disable Inactive Accounts

Shared

n/a

The information system automatically disables inactive accounts after [Assignment: organization-defined time period].

link

FedRAMP_High_R4

AC-2(7)

FedRAMP_High_R4_AC-2(7)

FedRAMP High AC-2 (7)

Access Control

Role-Based Schemes

Shared

n/a

The organization: (a) Establishes and administers privileged user accounts in accordance with a role-based access scheme that organizes allowed information system access and privileges into roles; (b) Monitors privileged role assignments; and (c) Takes [Assignment: organization-defined actions] when privileged role assignments are no longer appropriate. Supplemental Guidance: Privileged roles are organization-defined roles assigned to individuals that allow those individuals to perform certain security-relevant functions that ordinary users are not authorized to perform. These privileged roles include, for example, key management, account management, network and system administration, database administration, and web administration.

link

FedRAMP_High_R4

AC-6(9)

FedRAMP_High_R4_AC-6(9)

FedRAMP High AC-6 (9)

Access Control

Auditing Use Of Privileged Functions

Shared

n/a

The information system audits the execution of privileged functions. Supplemental Guidance: Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised information system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Auditing the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat (APT). Related control: AU-2.

link

FedRAMP_Moderate_R4

AC-2(3)

FedRAMP_Moderate_R4_AC-2(3)

FedRAMP Moderate AC-2 (3)

Access Control

Disable Inactive Accounts

Shared

n/a

The information system automatically disables inactive accounts after [Assignment: organization-defined time period].

link

FedRAMP_Moderate_R4

AC-2(7)

FedRAMP_Moderate_R4_AC-2(7)

FedRAMP Moderate AC-2 (7)

Access Control

Role-Based Schemes

Shared

n/a

link

FedRAMP_Moderate_R4

AC-6(9)

FedRAMP_Moderate_R4_AC-6(9)

FedRAMP Moderate AC-6 (9)

Access Control

Auditing Use Of Privileged Functions

Shared

n/a

link

hipaa

1109.01b1System.479-01.b

hipaa-1109.01b1System.479-01.b

1109.01b1System.479-01.b

11 Access Control

1109.01b1System.479-01.b 01.02 Authorized Access to Information Systems

Shared

n/a

User registration and deregistration, at a minimum: (i) communicates relevant policies to users and require acknowledgement (e.g., signed or captured electronically); (ii) checks authorization and minimum level of access necessary prior to granting access; (iii) ensures access is appropriate to the business needs (consistent with sensitivity/risk and does not violate segregation of duties requirements); (iv) addresses termination and transfer; (v) ensures default accounts are removed and/or renamed; (vi) removes or blocks critical access rights of users who have changed roles or jobs; and, (vii) automatically removes or disables inactive accounts.

hipaa

11220.01b1System.10-01.b

hipaa-11220.01b1System.10-01.b

11220.01b1System.10-01.b

11 Access Control

11220.01b1System.10-01.b 01.02 Authorized Access to Information Systems

Shared

n/a

User registration and de-registration formally address establishing, activating, modifying, reviewing, disabling and removing accounts.

hipaa

1129.01v1System.12-01.v

hipaa-1129.01v1System.12-01.v

1129.01v1System.12-01.v

11 Access Control

1129.01v1System.12-01.v 01.06 Application and Information Access Control

Shared

n/a

Access rights to applications and application functions should be restricted in accordance with the access control policy.

hipaa

1135.02i1Organizational.1234-02.i

hipaa-1135.02i1Organizational.1234-02.i

1135.02i1Organizational.1234-02.i

11 Access Control

1135.02i1Organizational.1234-02.i 02.04 Termination or Change of Employment

Shared

n/a

Upon termination or changes in employment for employees, contractors, third-party users, or other workforce arrangement, physical and logical access rights and associated materials (e.g., passwords, keycards, keys, documentation that identify them as current members of the organization) are removed or modified to restrict access within 24 hours and old accounts are closed after 90 days of opening new accounts.

hipaa

1145.01c2System.1-01.c

hipaa-1145.01c2System.1-01.c

1145.01c2System.1-01.c

11 Access Control

1145.01c2System.1-01.c 01.02 Authorized Access to Information Systems

Shared

n/a

Role-based access control is implemented and capable of mapping each user to one or more roles, and each role to one or more system functions.

hipaa

1151.01c3System.1-01.c

hipaa-1151.01c3System.1-01.c

1151.01c3System.1-01.c

11 Access Control

1151.01c3System.1-01.c 01.02 Authorized Access to Information Systems

Shared

n/a

The organization limits authorization to privileged accounts on information systems to a pre-defined subset of users.

hipaa

1152.01c3System.2-01.c

hipaa-1152.01c3System.2-01.c

1152.01c3System.2-01.c

11 Access Control

1152.01c3System.2-01.c 01.02 Authorized Access to Information Systems

Shared

n/a

The organization audits the execution of privileged functions on information systems and ensures information systems prevent non-privileged users from executing privileged functions.

hipaa

1214.09ab2System.3456-09.ab

hipaa-1214.09ab2System.3456-09.ab

1214.09ab2System.3456-09.ab

12 Audit Logging & Monitoring

1214.09ab2System.3456-09.ab 09.10 Monitoring

Shared

n/a

Monitoring includes privileged operations, authorized access or unauthorized access attempts, including attempts to access deactivated accounts, and system alerts or failures.

hipaa

1232.09c3Organizational.12-09.c

hipaa-1232.09c3Organizational.12-09.c

1232.09c3Organizational.12-09.c

12 Audit Logging & Monitoring

1232.09c3Organizational.12-09.c 09.01 Documented Operating Procedures

Shared

n/a

Access for individuals responsible for administering access controls is limited to the minimum necessary based upon each user's role and responsibilities and these individuals cannot access audit functions related to these controls.

hipaa

1270.09ad1System.12-09.ad

hipaa-1270.09ad1System.12-09.ad

1270.09ad1System.12-09.ad

12 Audit Logging & Monitoring

1270.09ad1System.12-09.ad 09.10 Monitoring

Shared

n/a

The organization ensures proper logging is enabled in order to audit administrator activities; and reviews system administrator and operator logs on a regular basis.

hipaa

1276.09c2Organizational.2-09.c

hipaa-1276.09c2Organizational.2-09.c

1276.09c2Organizational.2-09.c

12 Audit Logging & Monitoring

1276.09c2Organizational.2-09.c 09.01 Documented Operating Procedures

Shared

n/a

Security audit activities are independent.

hipaa

1451.05iCSPOrganizational.2-05.i

hipaa-1451.05iCSPOrganizational.2-05.i

1451.05iCSPOrganizational.2-05.i

14 Third Party Assurance

1451.05iCSPOrganizational.2-05.i 05.02 External Parties

Shared

n/a

Cloud service providers design and implement controls to mitigate and contain data security risks through proper separation of duties, role-based access, and least-privilege access for all personnel within their supply chain.

ISO27001-2013

A.12.4.1

ISO27001-2013_A.12.4.1

ISO 27001:2013 A.12.4.1

Operations Security

Event Logging

Shared

n/a

Event logs recording user activities, exceptions, faults and information security events shall be produced, kept and regularly reviewed.

link

ISO27001-2013

A.12.4.3

ISO27001-2013_A.12.4.3

ISO 27001:2013 A.12.4.3

Operations Security

Administrator and operator logs

Shared

n/a

System administrator and system operator activities shall be logged and the logs protected and regularly reviewed.

link

ISO27001-2013

A.9.2.3

ISO27001-2013_A.9.2.3

ISO 27001:2013 A.9.2.3

Access Control

Management of privileged access rights

Shared

n/a

The allocation and use of privileged access rights shall be restricted and controlled.

link

ISO27001-2013

A.9.2.4

ISO27001-2013_A.9.2.4

ISO 27001:2013 A.9.2.4

Access Control

Management of secret authentication information of users

Shared

n/a

The allocation of secret authentication information shall be controlled through a formal management process.

link

ISO27001-2013

A.9.3.1

ISO27001-2013_A.9.3.1

ISO 27001:2013 A.9.3.1

Access Control

Use of secret authentication information

Shared

n/a

Users shall be required to follow the organization's practices in the use of secret authentication information.

link

ISO27001-2013

A.9.4.3

ISO27001-2013_A.9.4.3

ISO 27001:2013 A.9.4.3

Access Control

Password management system

Shared

n/a

Password management systems shall be interactive and shall ensure quality password.

link

mp.s.2 Protection of web services and applications

404 not found

n/a

102

NIST_SP_800-171_R2_3

.1.2

NIST_SP_800-171_R2_3.1.2

NIST SP 800-171 R2 3.1.2

Access Control

Limit system access to the types of transactions and functions that authorized users are permitted to execute.

Shared

Microsoft and the customer share responsibilities for implementing this requirement.

Organizations may choose to define access privileges or other attributes by account, by type of account, or a combination of both. System account types include individual, shared, group, system, anonymous, guest, emergency, developer, manufacturer, vendor, and temporary. Other attributes required for authorizing access include restrictions on time-of-day, day-of-week, and point-of-origin. In defining other account attributes, organizations consider system-related requirements (e.g., system upgrades scheduled maintenance,) and mission or business requirements, (e.g., time zone differences, customer requirements, remote access to support travel requirements).

link

NIST_SP_800-171_R2_3

.1.7

NIST_SP_800-171_R2_3.1.7

NIST SP 800-171 R2 3.1.7

Access Control

Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.

Shared

Microsoft and the customer share responsibilities for implementing this requirement.

Privileged functions include establishing system accounts, performing system integrity checks, conducting patching operations, or administering cryptographic key management activities. Non-privileged users are individuals that do not possess appropriate authorizations. Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users. Note that this requirement represents a condition to be achieved by the definition of authorized privileges in 3.1.2. Misuse of privileged functions, either intentionally or unintentionally by authorized users, or by unauthorized external entities that have compromised system accounts, is a serious and ongoing concern and can have significant adverse impacts on organizations. Logging the use of privileged functions is one way to detect such misuse, and in doing so, help mitigate the risk from insider threats and the advanced persistent threat.

link

NIST_SP_800-53_R4

AC-2(3)

NIST_SP_800-53_R4_AC-2(3)

NIST SP 800-53 Rev. 4 AC-2 (3)

Access Control

Disable Inactive Accounts

Shared

n/a

The information system automatically disables inactive accounts after [Assignment: organization-defined time period].

link

NIST_SP_800-53_R4

AC-2(7)

NIST_SP_800-53_R4_AC-2(7)

NIST SP 800-53 Rev. 4 AC-2 (7)

Access Control

Role-Based Schemes

Shared

n/a

link

NIST_SP_800-53_R4

AC-6(9)

NIST_SP_800-53_R4_AC-6(9)

NIST SP 800-53 Rev. 4 AC-6 (9)

Access Control

Auditing Use Of Privileged Functions

Shared

n/a

link

NIST_SP_800-53_R5

AC-2(3)

NIST_SP_800-53_R5_AC-2(3)

NIST SP 800-53 Rev. 5 AC-2 (3)

Access Control

Disable Accounts

Shared

n/a

Disable accounts within [Assignment: organization-defined time period] when the accounts: (a) Have expired; (b) Are no longer associated with a user or individual; (c) Are in violation of organizational policy; or (d) Have been inactive for [Assignment: organization-defined time period].

link

NIST_SP_800-53_R5

AC-2(7)

NIST_SP_800-53_R5_AC-2(7)

NIST SP 800-53 Rev. 5 AC-2 (7)

Access Control

Privileged User Accounts

Shared

n/a

(a) Establish and administer privileged user accounts in accordance with [Selection: a role-based access scheme;an attribute-based access scheme] ; (b) Monitor privileged role or attribute assignments; (c) Monitor changes to roles or attributes; and (d) Revoke access when privileged role or attribute assignments are no longer appropriate.

link

NIST_SP_800-53_R5

AC-6(9)

NIST_SP_800-53_R5_AC-6(9)

NIST SP 800-53 Rev. 5 AC-6 (9)

Access Control

Log Use of Privileged Functions

Shared

n/a

Log the execution of privileged functions.

link

op.acc.1 Identification

404 not found

n/a

op.acc.2 Access requirements

404 not found

n/a

op.acc.3 Segregation of functions and tasks

404 not found

n/a

op.acc.4 Access rights management process

404 not found

n/a

op.acc.5 Authentication mechanism (external users)

404 not found

n/a

op.exp.10 Cryptographic key protection

404 not found

n/a

op.exp.8 Recording of the activity

404 not found

n/a

PCI_DSS_v4.0

10.2.1.2

PCI_DSS_v4.0_10.2.1.2

PCI DSS v4.0 10.2.1.2

Requirement 10: Log and Monitor All Access to System Components and Cardholder Data

Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events

Shared

n/a

Audit logs capture all actions taken by any individual with administrative access, including any interactive use of application or system accounts.

link

PCI_DSS_v4.0

10.2.1.3

PCI_DSS_v4.0_10.2.1.3

PCI DSS v4.0 10.2.1.3

Requirement 10: Log and Monitor All Access to System Components and Cardholder Data

Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events

Shared

n/a

Audit logs capture all access to audit logs.

link

PCI_DSS_v4.0

10.2.1.5

PCI_DSS_v4.0_10.2.1.5

PCI DSS v4.0 10.2.1.5

Requirement 10: Log and Monitor All Access to System Components and Cardholder Data

Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events

Shared

n/a

Audit logs capture all changes to identification and authentication credentials including, but not limited to: • Creation of new accounts. • Elevation of privileges. • All changes, additions, or deletions to accounts with administrative access.

link

PCI_DSS_v4.0

10.2.1.6

PCI_DSS_v4.0_10.2.1.6

PCI DSS v4.0 10.2.1.6

Requirement 10: Log and Monitor All Access to System Components and Cardholder Data

Audit logs are implemented to support the detection of anomalies and suspicious activity, and the forensic analysis of events

Shared

n/a

Audit logs capture the following: • All initialization of new audit logs, and • All starting, stopping, or pausing of the existing audit logs.

link

PCI_DSS_v4.0

10.6.3

PCI_DSS_v4.0_10.6.3

PCI DSS v4.0 10.6.3

Requirement 10: Log and Monitor All Access to System Components and Cardholder Data

Time-synchronization mechanisms support consistent time settings across all systems

Shared

n/a

Time synchronization settings and data are protected as follows: • Access to time data is restricted to only personnel with a business need. • Any changes to time settings on critical systems are logged, monitored, and reviewed.

link

PCI_DSS_v4.0

8.2.6

PCI_DSS_v4.0_8.2.6

PCI DSS v4.0 8.2.6

Requirement 08: Identify Users and Authenticate Access to System Components

User identification and related accounts for users and administrators are strictly managed throughout an account’s lifecycle

Shared

n/a

Inactive user accounts are removed or disabled within 90 days of inactivity.

link

SOC_2

CC6.3

SOC_2_CC6.3

SOC 2 Type 2 CC6.3

Logical and Physical Access Controls

Rol based access and least privilege

Shared

The customer is responsible for implementing this recommendation.

• Creates or Modifies Access to Protected Information Assets — Processes are in place to create or modify access to protected information assets based on authorization from the asset’s owner. • Removes Access to Protected Information Assets — Processes are in place to remove access to protected information assets when an individual no longer requires access. • Uses Role-Based Access Controls — Role-based access control is utilized to support segregation of incompatible functions. • Reviews Access Roles and Rules — The appropriateness of access roles and access rules is reviewed on a periodic basis for unnecessary and inappropriate individuals with access and access rules are modified as appropriate

SWIFT_CSCF_v2022

1.2

SWIFT_CSCF_v2022_1.2

SWIFT CSCF v2022 1.2

1. Restrict Internet Access & Protect Critical Systems from General IT Environment

Restrict and control the allocation and usage of administrator-level operating system accounts.

Shared

n/a

Access to administrator-level operating system accounts is restricted to the maximum extent possible. Usage is controlled, monitored, and only permitted for relevant activities such as software installation and configuration, maintenance, and emergency activities. At all other times, an account with the least privilege access is used.

link

SWIFT_CSCF_v2022

5.1

SWIFT_CSCF_v2022_5.1

SWIFT CSCF v2022 5.1

5. Manage Identities and Segregate Privileges

Enforce the security principles of need-to-know access, least privilege, and separation of duties for operator accounts.

Shared

n/a

Accounts are defined according to the security principles of need-to-know access, least privilege, and separation of duties.

link

Initiative DisplayName