Benchmark: 3.1.i Public Key Infrastructure (PKI)
Description
NBFCs may increase the usage of PKI to ensure confidentiality of data, access control, data integrity, authentication and nonrepudiation.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-aws-complianceStart the Powerpipe server:
steampipe service startpowerpipe serverOpen http://localhost:9033 in your browser and select 3.1.i Public Key Infrastructure (PKI).
Run this benchmark in your terminal:
powerpipe benchmark run aws_compliance.benchmark.rbi_itf_nbfc_3_1_iSnapshot and share results via Turbot Pipes:
powerpipe benchmark run aws_compliance.benchmark.rbi_itf_nbfc_3_1_i --shareControls
- ACM certificates should not expire within 30 days
- API Gateway stage should uses SSL certificate
- ELB application load balancers should be drop HTTP headers
- ELB application load balancers should redirect HTTP requests to HTTPS
- ELB application and network load balancers should only use SSL or HTTPS listeners
- ELB classic load balancers should use SSL certificates
- ELB classic load balancers should only use SSL or HTTPS listeners
- OpenSearch domains should use HTTPS
- Redshift cluster encryption in transit should be enabled
- S3 buckets should enforce SSL