AWS Well-Architected Security Pillar
Identity & Access Management

AWS Well-Architected Security Pillar SEC03-BP09: Share resources securely with a third party

When granting third-party access use IAM roles with external ID, condition keys, time bound credentials and contractual controls rather than long-lived IAM users.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 43 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-161 Rev 1 · 5 controls

FedRAMP High · 4 controls

  • AC-20 Use of External Systems
  • AC-20(1) Limits on Authorized Use
  • CA-3 Information Exchange
  • SA-9 External System Services

FedRAMP Moderate · 4 controls

  • AC-20 Use of External Systems
  • AC-20(1) Limits on Authorized Use
  • CA-3 Information Exchange
  • SA-9 External System Services

NIST SP 800-53 Rev 5 · 4 controls

ISO 27001:2022 · 3 controls

  • 5.14 Information transfer
  • 5.19 Information security in supplier relationships
  • 5.20 Addressing information security within supplier agreements

ISO 27002:2022 · 3 controls

  • 5.14 Information transfer
  • 5.19 Information security in supplier relationships
  • 5.20 Addressing information security within supplier agreements

NIST SP 800-171 Rev 3 · 3 controls

C5 (Germany) · 2 controls

  • C5-IDM-07 Access to cloud customer data
  • C5-SSO-01 Policies and instructions for controlling and monitoring third parties

HIPAA Security Rule · 2 controls

  • NIST-CSF-DE.CM-06 External service provider activities and services are monitored to find potentially adverse events
  • NIST-CSF-GV.SC-05 Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties
  • ANSSI-HYG-25 Secure Dedicated Network Interconnections with Partners
  • ASBv3-PA-8 Determine access process for cloud provider support

CIS Controls v8 · 1 control

  • CIS-15.4 Ensure Service Provider Contracts Include Security Requirements

CMMC 2.0 · 1 control

ISO 27701:2019 · 1 control

  • 6.12.1 Information security in supplier relationships
  • 164.308(b)(1) Business Associate Contracts and Other Arrangements (Standard)

PCI DSS 4.0 · 1 control

  • 8.2.7 8.2.7 Third-party remote access accounts controlled

SOC 2 · 1 control

  • SOC2-CC9.2 CC9.2 Assessing and managing vendor and business partner risk

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Identity & Access Management

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC03-BP09 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 43 it maps to, and the evidence behind each claim, over MCP and REST.