DigitalXForce

Home » Integration » AWS Integration

AWS integration

DigitalXForce wrote this page.

DigitalXForce connects to your AWS accounts, evaluates their configurations directly and takes in findings from cloud security posture management (CSPM) tools, which it maps to controls. It maps each result once across 50+ compliance frameworks. A failed control result reaches the compliance view, the posture view and the risk register at the same time.

The integration serves security, cloud and GRC teams that run workloads on AWS and have to show that cloud controls hold between audits, in the same record as the rest of the estate. It is part of the ESRPM module, which connects to AWS, Azure and GCP accounts in the same way, so DigitalXForce has a CSPM capability inside the platform.

How does Continuous Control Assurance (CCA) work with cloud platforms?

Continuous Control Assurance (CCA) uses evidence, monitoring and validation to determine whether controls continue to operate as expected. Continuous Control Monitoring (CCM) monitors conditions, evidence and signals associated with controls. CCM is a capability within CCA.

Cloud controls change as fast as the infrastructure they govern, so a yearly review sees little of their real history. The AWS integration supplies the evidence. Continuous Control Monitoring watches the configuration conditions and signals it carries, and Continuous Control Assurance uses them to determine whether each cloud control continues to operate as expected.

Which AWS services hold the evidence for cloud controls?

AWS is one of the three cloud connectors in DigitalXForce’s connector table, with Microsoft Azure and GCP. The integrations page lists two AWS connectors, AWS and AWS CodeCommit, among 250+ technology integrations.

Enterprise Security Risk and Posture Management (ESRPM) is the DigitalXForce module that runs configuration checks, operational insights and deployment benchmarking across IAM, SIEM, cloud, OT and IoT, SecOps and enterprise systems through 250+ technology integrations.

AWS documents the services below as places where an account’s control evidence lives, and each one answers a question an auditor asks about cloud controls.

AWS serviceWhat AWS says it recordsThe control question it answers
AWS ConfigAWS Config gives a detailed view of the configuration of the AWS resources in an account, including how they relate to one another and how their configurations and relationships change over time.Are cloud resources configured to the baseline, and has anything drifted?
AWS Identity and Access Management (IAM)IAM controls who is authenticated and who is authorized to use each AWS resource.Do only the right identities have access, with no more permission than they need?
AWS CloudTrailCloudTrail records actions taken by a user, a role or an AWS service as events, and its event history keeps the past 90 days of management events.Is activity in the account logged and kept?
AWS Security Hub CSPMSecurity Hub CSPM runs checks against security controls in standards such as AWS Foundational Security Best Practices, CIS, PCI DSS and NIST, and it receives findings from services such as Amazon GuardDuty, Amazon Inspector and Amazon Macie.What do AWS’s own posture checks already report about the account?

What does DigitalXForce do with the evidence?

  1. It tests the control. Each piece of evidence tests the control it answers, and DigitalXForce maps each control once to every framework requirement it satisfies across 50+ compliance frameworks, so one test counts toward all of them.
  2. It sends the result to every view at once. A failed control result reaches the compliance view, the posture view and the risk register at the same time, because the 15 modules share one data layer.
  3. It scores the risk. AI JedAI is the DigitalXForce AI engine that analyzes: it reasons over control evidence and live telemetry, maps documents to controls and frameworks, scores and prioritizes risk, and recommends remediation mapped to framework requirements. It analyzes signals from cloud, endpoint, identity, SaaS and network telemetry to detect control drift, and it scores and prioritizes the risk in the register.
  4. It updates posture. The Digital Trust Score is DigitalXForce’s composite score from 300 to 850, computed continuously from live control evidence across seven sub-postures: security, compliance, audit, resilience, third-party, AI and risk. Its security sub-posture covers control validation, attacker exposure, identity, and detection and containment.
  5. It hands the fix to people. A risk operations center is an operating model for continuously measuring, prioritizing and reducing risk, in the way a security operations center handles threats; DigitalXForce’s implementation is X-ROC, the XForce Risk Operations Center. X-ROC is the operations layer of the DigitalXForce TRiSCM platform, where control failures, risk changes and vendor events are alerted, triaged, escalated and reported. X-ROC never changes a customer’s systems on its own, so remediation is assigned and tracked in X-ROC and the change itself is made by the customer’s own team.
  6. It reports. XForce GPT is the DigitalXForce generative AI engine that writes: it produces the plain-language risk narratives and board-ready reports, generates policies, standards and plans, and runs the embedded assistant. It writes those narratives and reports from the same record as every test result.

Which framework requirements does AWS evidence answer?

Cloud configuration, access, logging and encryption appear in every major security framework. AWS evidence answers requirements such as these, among the 50+ compliance frameworks DigitalXForce maps.

FrameworkWhat the cloud evidence answers
NIST CSF 2.0PR.PS-01 asks that configuration management practices are established and applied, PR.DS-01 asks that the confidentiality, integrity and availability of data at rest are protected, and PR.PS-04 asks that log records are generated and made available for continuous monitoring.
NIST SP 800-53 Rev. 5CM-6 covers configuration settings, AC-6 covers least privilege, AU-2 covers event logging, and SC-28 covers protection of information at rest.
CIS ControlsControl 4 covers the secure configuration of enterprise assets and software, and Control 8 covers collecting, reviewing and retaining audit logs.
ISO/IEC 27001:2022Annex A control 5.23 covers information security for the use of cloud services, 8.9 covers configuration management, 8.15 covers logging, and 8.24 covers the use of cryptography.
PCI DSS v4.0.1Requirement 2.2.1 asks for configuration standards for system components, and requirement 10.2.1 asks that audit logs are enabled and active.
SOC 2Criterion CC6.1 covers logical access security, and CC7.1 covers detecting configuration changes that introduce new vulnerabilities.

Each control is mapped once, so the same cloud evidence answers all of these requirements at the same time.

How is the AWS connection set up?

The customer connects each AWS account with access it creates in that account and keeps under its own control. This integration is agentless, so nothing is installed on the workloads it evaluates, and integrations are API-based and read-only where the source allows it. Connectors read configuration and compliance signals only, never business records or customer data.

AWS’s own guidance for giving a third party access to an account is an IAM role that the account owner creates. The role’s trust policy names the third party’s AWS account and an external ID, and its permission policy sets what the third party may do.

DigitalXForce’s standard proof of value runs for 4 weeks on the customer’s own systems and frameworks. Connectors are configured in week 1, the attack surface and External Risk View are set up in week 2, the first assessments run in week 3, and they are reviewed with the customer in week 4.

Where is the AWS integration not the answer?

DigitalXForce reads cloud configuration and posture findings as control evidence, and cloud is one of its connector domains rather than the platform’s purpose. Protecting running workloads inside the cloud is the job of a cloud workload protection tool, and DigitalXForce does not claim that role.

AWS Security Hub CSPM already checks AWS accounts against standards such as AWS Foundational Security Best Practices, CIS, PCI DSS and NIST. DigitalXForce builds the platform on a Cybersecurity Mesh Architecture, so it connects to the tools an enterprise already runs and works across them, rather than replacing them. It fits when cloud evidence has to count toward many frameworks at once, next to identity, endpoint and vulnerability evidence.

Questions about the AWS integration

How does Continuous Control Assurance (CCA) integrate with cloud platforms?

Continuous Control Assurance (CCA) uses evidence, monitoring and validation to determine whether controls continue to operate as expected. For cloud platforms, DigitalXForce connects to AWS, Azure and GCP accounts, evaluates their configurations directly and takes in findings from cloud security posture management tools, which it maps to controls. A failed control result reaches the compliance view, the posture view and the risk register at the same time.

What does DigitalXForce read from AWS?

DigitalXForce connects to your AWS accounts and evaluates their configurations directly, and it also takes in findings from cloud security posture management tools and maps them to controls. Each result tests a control, and each control is mapped once across 50+ compliance frameworks. Connectors read configuration and compliance signals only, never business records or customer data.

Does DigitalXForce replace AWS Security Hub CSPM?

It does not. AWS Security Hub CSPM checks AWS accounts against standards such as AWS Foundational Security Best Practices, CIS, PCI DSS and NIST. DigitalXForce tests the same accounts against controls mapped once across 50+ compliance frameworks, on the same record as your identity, endpoint and vulnerability evidence.

Does DigitalXForce connect to Microsoft Azure and Google Cloud as well?

It does. The ESRPM module connects to AWS, Azure and GCP accounts and evaluates their configurations the same way.

Is DigitalXForce available on AWS Marketplace?

It is. AWS Marketplace lists DigitalXForce as a software as a service product sold by DigitalXForce Corporation.

Where is DigitalXForce hosted?

DigitalXForce is a cloud-native SaaS platform hosted on AWS, with encryption in transit and at rest. It reaches on-premises, hybrid and private cloud systems through API-based integrations.

What happens when a cloud control fails?

A failed control result reaches the compliance view, the posture view and the risk register at the same time. AI JedAI scores and prioritizes the risk, and remediation is assigned and tracked in X-ROC, the XForce Risk Operations Center, while your own team makes the change.

Amazon Web Services, AWS and the AWS service names are trademarks of Amazon.com, Inc. or its affiliates. Naming them here describes a connector and does not imply a partnership.

Sources

What this looks like in practice.

Reading about continuous evidence is one thing. Watching a control get tested against live data from your own stack is another. A 30 minute walkthrough on your frameworks shows the difference.

Request a demo

Scroll to Top
Title banner reading Era of Automated Security Risk and Posture Management with the DigitalXForce logo beside a hand holding connected user icons and a report

Era of Automated Security Risk and Posture Management

Title banner reading Era of Automated Third Party Risk Management with Trust but Verify, with the DigitalXForce logo beside a hand holding connected user icons and a report

Era of Automated Third Party Risk Management: Trust but Verify

Title banner reading Era of Automated Security Plans, Standards, Policies and Procedures, with the DigitalXForce logo beside a hand holding connected user icons and a report

Era of Automated Security Plans, Standards, Policies and Procedures