Infrastructure Security in Control Catalog
As a managed service, Control Catalog is protected by the AWS global network security
procedures that are described in the Amazon Web Services: Overview of Security Processes
You use AWS published API calls to access Control Catalog through the network. Clients must support Transport Layer Security (TLS) 1.0 or later. We recommend TLS 1.2 or later. Clients must also support cipher suites with perfect forward secrecy (PFS) such as DHE (Ephemeral Diffie-Hellman) or ECDHE (Elliptic Curve Ephemeral Diffie-Hellman). Most modern systems such as Java 7 and later support these modes.
Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the AWS Security Token Service (AWS STS) to generate temporary security credentials to sign requests.
Configuration and vulnerability analysis in Control Catalog
Configuration and IT controls are a shared responsibility between AWS and you, our customer. For more information, see the AWS shared responsibility
model
