Skip to main content

💼 [EC2.56] VPCs should be configured with an interface endpoint for Docker Registry

  • Contextual name: 💼 [EC2.56] VPCs should be configured with an interface endpoint for Docker Registry
  • ID: /frameworks/aws-fsbp-v1.0.0/ec2/56
  • Located in: 💼 Elastic Compute Cloud (EC2)

Description​

AWS PrivateLink enables customers to access services hosted on AWS in a highly available and scalable manner, while keeping all the network traffic within the AWS network. Service users can privately access services powered by PrivateLink from their VPC or their on-premises, without using public IPs, and without requiring traffic to traverse across the internet.

Similar​

Similar Sections (Give Policies To)​

SectionSub SectionsInternal RulesPoliciesFlags
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement15417
💼 NIST SP 800-53 Revision 5 → 💼 AC-3(7) Access Enforcement _ Role-based Access Control7
💼 NIST SP 800-53 Revision 5 → 💼 AC-4 Information Flow Enforcement326173
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(21) Information Flow Enforcement _ Physical or Logical Separation of Information Flows3539
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege102126
💼 NIST SP 800-53 Revision 5 → 💼 AC-21 Information Sharing22
💼 NIST SP 800-53 Revision 5 → 💼 SC-7 Boundary Protection29533
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(3) Boundary Protection _ Access Points2
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(4) Boundary Protection _ External Telecommunications Services17
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(11) Boundary Protection _ Restrict Incoming Communications Traffic15
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(16) Boundary Protection _ Prevent Discovery of System Components16
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(20) Boundary Protection _ Dynamic Isolation and Segregation2
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(21) Boundary Protection _ Isolation of System Components16

Sub Sections​

SectionSub SectionsInternal RulesPoliciesFlags