Cloud Scanner Overview
ThreatStryker performs Compliance Posture Scanning to:
- Build an inventory of cloud assets, such as network security groups, storage objects, key management services. The types of assets discovered are specific to each cloud platform.
- Perform 'posture scanning', where ThreatStryker matches infrastructure configuration against a set of best-practice benchmarks, such as CIS, PCI-DSS and HIPAA. The benchmarks that are supported are specific to each cloud platform.
ThreatStryker then summarises the results in a 'Threat Graph' visualization, to help you to prioritize compliance issues that pose the greatest risk of exploit.
- Compliance Posture Scanning for Clouds requires access (typically read-only) to the cloud platform APIs, and uses the Cloud Scanner task
- Compliance Posture Scanning for Hosts requires direct access to the host, and uses the Sensor Agent container.
Compliance Posture Scanning for Clouds
The ThreatStryker Console does not access the cloud platform APIs directly; there is no need to open the APIs up for remote access. Instead, you deploy a 'Cloud Scanner' task which acts as a local relay, taking instructions from the remote ThreatStryker console and performing local API calls from within your cloud infrastructure.
Each Cloud Scanner task runs in your cloud environment, gathering inventory and compliance information for the assets deployed in that environment. It submits that information to your ThreatStryker console. You can deploy as many Cloud Scanner tasks as are required by your security policy and any restrictions in place that affect API access.
Cloud Scanner tasks are deployed using the appropriate Terraform module for each cloud, and are configured with the address and API key of your management console. They 'phone home' to your management console and take instructions on demand; they do not listen for remote connections or control.
Refer to the Installation Documentation to Learn how to install Cloud Scanner tasks
Compliance Posture Scanning for Hosts
ThreatStryker can perform compliance posture scanning on linux hosts and Kubernetes master and worker nodes.
Scanning is done directly, using a local Sensor Agent rather than by using the Cloud Scanner task employed by the cloud platform integrations.