Administering Keen
Cloud vendor posture
Chapter 13 of 40
Cloud vendor posture
Cloud vendor posture reads how your cloud services are set up, such as who holds administrator rights and who signs in without MFA, and what happens in them, such as sign-ins and changes to users. Keen records each result and activity entry as evidence, so mapping rules can attach them to controls, and shows the latest results on the provider's vendor page.
Each provider reads one or more scopes, such as AWS accounts, with read-only credentials. Providers: AWS, Microsoft Entra ID and Azure, Google Cloud, Google Workspace, Akamai Cloud (Linode), DigitalOcean and Scaleway.
Turn a provider on
Each provider is configured in the deployment environment: its KEEN_<PROVIDER>_ENABLED setting, read-only credentials and the scopes to read. The provider's chapter lists its settings and how to create credentials that can only read what Keen needs. Recreate the API, worker and beat containers after changing them. The scheduler reads a newly enabled provider within about 15 minutes; to read it at once, choose its button under Admin → Ingest runners → Cloud vendor posture, which refreshes the checks and reads recent activity. An enabled provider appears in Admin → Sources under Source catalogue and collection health, with its event count, and can be paused there like any other source.
Where the results appear
On its first refresh, even one that fails, a provider links to a vendor in the Vendors register: one named after the provider, ignoring case (for AWS, Amazon Web Services, AWS or Amazon Web Services, Inc.; for Microsoft, Microsoft, Microsoft Azure, Microsoft 365 or Microsoft Corporation; for Google Cloud, Google Cloud, Google or Google LLC; for Google Workspace, Google Workspace, Google or Google LLC; for Akamai Cloud, Akamai (Linode), Linode, Akamai, Akamai Cloud or Akamai Technologies; for DigitalOcean, DigitalOcean, Digital Ocean or DigitalOcean, LLC; for Scaleway, Scaleway or Scaleway SAS), or a new one Keen creates with the provider's name and website. Edit or rename that vendor freely; Keen keeps showing the provider there. Two providers can share one vendor, such as both Google providers on a vendor named Google. If the vendor is deleted, the next refresh links or creates one again.
The vendor's Cloud posture tab shows each scope's checks with their result and detail, and links each result to its evidence. Choose the count under a check to see the users or resources it lists. Each scope also lists the identities the provider reports, with their administrator rights, MFA and last use; an identity whose email matches a person in the People register links to that person. Recent activity lists the provider's latest activity events, and View all opens them on the Events page. People need ISMS read access and the events.read permission to see the tab. Administrators can choose Refresh now, which refreshes the checks and reads recent activity; Keen accepts one refresh request per provider every two minutes, from here or from Ingest runners.
A check reads Not established when Keen could not read it, and names the reason: the credentials are not allowed to read it, the provider's plan for that scope does not include it, it is not set up for that scope, or the provider did not answer. The provider's other checks carry on. When a whole refresh fails, for example because the credentials are wrong, the tab keeps the last results and shows the reason.
A check that counts users or resources and finds none, such as the Kubernetes check in an account with no clusters, is left out: the tab shows no result for it and Keen records no event, so it never counts as evidence. A scope whose checks are all left out says there is nothing in it to check yet.
Schedule
| Setting | Effect |
|---|---|
KEEN_CLOUD_POSTURE_POLL_SECONDS | How often each provider's checks refresh, from 3600 to 86400 seconds; 43200 (12 hours) by default. The scheduler looks every 15 minutes for a provider that is due, so a newly enabled provider is read soon after start-up. |
KEEN_CLOUD_ACTIVITY_POLL_SECONDS | How often each provider's activity is read, from 300 to 86400 seconds; 1800 (30 minutes) by default. |
KEEN_CLOUD_INACTIVE_DAYS | Users with no recorded use for this many days need attention; 45 by default. A user never used counts from its creation. |
KEEN_CLOUD_KEY_AGE_DAYS | Access keys older than this many days need attention; 90 by default. |
An activity read starts where the last one ended, or one day back on the first read and after a longer pause, and covers at most six hours, so a provider that has fallen behind catches up over the following reads. Each entry is stored once, under the provider's own ID. A read keeps at most 1,000 entries; when a window holds more, Keen keeps the newest and the vendor page says so. Results older than two refresh intervals are marked as such on the vendor page, and results not refreshed for 30 days are removed with their identities.
Evidence and mapping
Each check result is an event whose source is the provider, such as aws; whose action is posture. followed by the check, such as posture.identity.mfa; and whose outcome is the result: met, attention or info. Its system names the provider and scope, such as aws:111122223333, and its data lists the result's detail and the users or resources it names. Keen records a result when it changes and once a day while it holds, so the evidence shows the state on each day; a check Keen could not read records nothing.
Activity events keep the provider's own action name, such as ConsoleLogin or CreateUser, with the person or role that acted, an outcome of success, failure or info, and the provider's own record as the event's artifact. Keen's built-in rules map the checks to the Keen Assurance Framework; map activity, or checks to other controls, with ordinary mapping rules. Checks with the same name mean the same thing for every provider, so one rule on the action can map them all:
| Action | Check |
|---|---|
posture.identity.mfa | Every person who signs in uses MFA. |
posture.identity.admin_mfa | Every administrator uses MFA. |
posture.identity.mfa_enforced | MFA is required at sign-in. |
posture.identity.admins | Who holds administrator rights; reported for information. |
posture.identity.guests | How many guest accounts there are; reported for information. |
posture.identity.inactive | No user has gone unused for KEEN_CLOUD_INACTIVE_DAYS. |
posture.credentials.key_age | No active access key is older than KEEN_CLOUD_KEY_AGE_DAYS. |
posture.logging.audit_trail | The provider's audit log is recorded. |
posture.storage.public_access | Storage is protected from public access. |
posture.network.admin_ports | No firewall rule lets SSH or RDP in from the whole internet. |
posture.network.databases | No managed database accepts connections from the whole internet. |
posture.network.firewall_coverage | Every server is behind one of the provider's firewalls. |
posture.resilience.backups | Every server or managed database has the provider's automatic backups on. |
posture.kubernetes.control_plane | Every managed Kubernetes cluster's control plane meets the provider's chapter, such as high availability, automatic upgrades or an access list. |
posture.findings | The provider's own security service reports no open critical or high findings. |
Each provider's chapter lists the checks it runs, including any of its own.
Record a risk
Each account, subscription, project or domain a provider reports is an asset under Cloud services, supplied by the provider's vendor, from its first refresh, so risks and the access control matrix can name it. Keen leaves an existing asset as it is, so you can rename it or move it to another category; one you delete returns with the next refresh while the provider still reports it.
A check that needs attention offers Create a risk to people who manage risks, as does each user or resource it lists. Keen adds the risk to the scope's asset and links it to the controls the check's evidence maps to in the selected framework. Accepted with an owner and a review date, the risk shows the check, or the listed item, as Risk accepted until that date. A check reads Risk accepted when every item it lists has an accepted risk.
Once the risk is closed, the check or the listed item reads Risk treated while it fails as it did when the risk closed, in a neutral colour. A user or resource the check lists afterwards, or one that passes and later fails again, needs attention again, and so does a check that fails for more of them than before or passes and later fails again; the closed risk then shows Risk closed before this failure began, and Risk closed while the check passes. A check reads Risk treated when every item it lists has an accepted risk or a risk that treats it. Keen dates each failure by its own clock as each refresh reads it; a failure stored before Keen dated failures is dated from the refresh that read it, so a risk closed since then treats it.
Demo mode. In demo mode Keen never contacts a cloud provider: each provider answers with fictional scopes, results and activity.