AWS

Turn findings from AWS security services into risks and security signals, and copy CloudTrail events into the audit log.

The AWS connector reads from six AWS services in one account and region. Each service has its own Sync button, so you decide which findings come in and when. Nothing is written back to AWS: the connector only reads.

At a glance

Direction Into Aegis.
What it brings in Security Hub, Inspector, AWS Config (non-compliant resources) and IAM Access Analyzer findings; GuardDuty findings; CloudTrail events.
Where it lands Security Hub, Inspector, Config and Access Analyzer findings become risks (Inspector with CVE links). GuardDuty findings go to the security signal inbox (/incidents/signals) for review; a sync never creates an incident. CloudTrail events that matter for security are written to the audit log.
Credentials and permissions An access key of an IAM user (optionally assuming a role in another account) with securityhub:GetFindings, inspector2:ListFindings, config:DescribeComplianceByConfigRule, config:DescribeConfigRules, access-analyzer:ListAnalyzers, access-analyzer:ListFindingsV2, guardduty:ListDetectors, guardduty:ListFindings, guardduty:GetFindings, cloudtrail:LookupEvents and sts:GetCallerIdentity.
Owner of imported records Risks belong to the person who ran the sync. Signals have no owner until a reviewer accepts one. CloudTrail audit entries are recorded against the person who ran the sync, with the AWS user named in the entry.
When it runs On demand, per service, from the connector page or the API. AWS has no scheduled sync.
Set it up /connectors/aws, by people allowed to configure connectors (Manager or above), on a plan that includes the connector.

Who uses it

The page opens for Manager and Admin users. A Contributor or Viewer who opens /connectors/aws is sent to the /unauthorized page.

What's on this screen

No screenshot of this page was captured for this edition of the guide. The page reads from top to bottom in this order:

Connect your AWS account

  1. In AWS IAM, create a user for Aegis with the read permissions listed in Required IAM Permissions, and create an access key for it. Copy the secret access key straight away; AWS shows it only once. To read another account, also create a role there that this user may assume.
  2. In Aegis, enter the Access Key ID (it starts with AKIA) and the Secret Access Key. When a secret is already stored, the field shows dots; leave it blank to keep the stored secret.
  3. Choose the Region where your security services run. The list offers sixteen AWS regions and starts on EU (Ireland) (eu-west-1); Aegis refuses any region not in that list.
  4. If Aegis should work through a role, paste its ARN into Assume Role ARN, for example arn:aws:iam::123456789012:role/AegisConnectorRole. Leave it empty to use the IAM user directly.
  5. Select Save Configuration. The button stays disabled until the access key ID and region are filled in. After saving, Connection Status reads Not Tested and Test Connection appears.
  6. Select Test Connection. Aegis asks AWS who the key belongs to. On success the panel shows Connected to AWS with the account ID, region and identity, plus Role Assumed: Yes when a role was used, and AWS Security Services appears below. On failure the panel shows the error instead.
The secret is needed for every test and sync

You can save the form without a secret access key, but the test and every sync then stop with a missing-credentials error. Once saved, the secret is never shown again; to rotate it, type the new value and save.

Run a sync

  1. In AWS Security Services, find the service you want and read its Syncs to: line: Risks, Incidents (GuardDuty) or Audit Log (CloudTrail).
  2. Select that row's Sync. The button changes to Syncing... with a spinner while Aegis reads from AWS. Other services can be synced at the same time.
  3. Read the result box under the row. Sync Complete with the time shows how many records were created, and how many were skipped or failed; an Inspector sync also counts the distinct CVEs. Sync Failed shows the error, for example when AWS rejects the credentials.
  4. Open the records: Risks for the four risk-producing services, the security signal inbox under Incidents for GuardDuty, and the Audit Log for CloudTrail.

Once the connector has synced, the page shows Last successful sync: with the date and time of the last completed sync, and it still does after a reload. The counts of a sync are shown only for the visit in which you ran it; the audit log records every sync.

What each sync brings in

A sync from the page uses the defaults below. Through the API, every sync accepts a maximum number of results; GuardDuty, Security Hub and Inspector also accept severities; and the four risk-producing services accept the risk category for new risks. The page itself has no filter controls.

Service What a sync from the page reads What it creates
GuardDuty Up to 50 findings rated CRITICAL or HIGH. Security signals for review. Findings already in the inbox, or already imported as incidents, are skipped.
Security Hub Up to 50 active findings with workflow status NEW, rated CRITICAL, HIGH or MEDIUM. Open risks.
AWS Config Up to 50 rule evaluations with status NON_COMPLIANT. Open risks for the non-compliant resources.
IAM Analyzer Up to 50 active Access Analyzer findings. Open risks.
Inspector Up to 50 active findings rated CRITICAL, HIGH or MEDIUM. Open risks with their CVE identifiers.
CloudTrail Up to 50 events from the last 24 hours. Audit log entries for security-relevant events only — for example IAM user, role, policy and access-key changes, console sign-ins, trail changes, security-group changes, key deletion and bucket-policy changes. Other events are counted as skipped.

For Security Hub and Inspector, the AWS severity sets impact and likelihood on the standard scale: CRITICAL 5 × 5, HIGH 4 × 4, MEDIUM 3 × 3, LOW 2 × 2 and INFORMATIONAL 1 × 1. AWS Config risks are always scored 3 × 3. IAM Analyzer risks are scored 5 × 4 when the finding grants public access, and 3 × 3 otherwise. Review the scores after a sync; they are a starting point, not an assessment. Without a category in the request, Aegis picks the first risk category whose name fits the service (such as “cloud”, “technical”, “vulnerability”, “configuration” or “access”), or else your first category. A finding that already has a risk from an earlier sync is skipped, so running a sync again does not create duplicates.

Disconnect the connector

  1. As an Admin, go to Disconnect connector at the foot of the page. It explains that the stored AWS configuration and credentials are deleted, and that records already imported stay in Aegis.
  2. Select Disconnect. A confirmation dialog asks you to confirm.
  3. Confirm with Disconnect. The configuration is removed, the action is recorded in the audit log, and you return to the Connectors overview. You can configure AWS again later.

Tips and limits

Where this connects

Imported risks are worked in Risks; signals in Incidents; CloudTrail entries are read in the Audit Log. For the connector overview and the status dots, see Connectors.