Administering Keen
Akamai Cloud (Linode)
Chapter 17 of 40
Akamai Cloud (Linode)
Akamai Cloud posture reads the Linode account a personal access token belongs to: its users and their two-factor authentication, Cloud Firewalls, Linode backups, managed databases and LKE clusters, with read-only access, and records Cloud Manager sign-ins and account events. Results appear on the Akamai (Linode) vendor's Cloud posture tab (see Cloud vendor posture).
Keen reads api.linode.com through its validated HTTP client and names the account after its external unique ID, with the company name as its label.
Checks
| Check | Action | Met when |
|---|---|---|
| Two-factor authentication | posture.identity.mfa | Every user has two-factor authentication on. |
| Two-factor authentication for unrestricted users | posture.identity.admin_mfa | Every unrestricted user has two-factor authentication on. |
| Unrestricted users | posture.identity.admins | Reported for information: the users with unrestricted access to the account. |
| Unused users | posture.identity.inactive | No user's latest successful sign-in is older than KEEN_CLOUD_INACTIVE_DAYS. A user who has never signed in counts from when their password was set. |
| SSH and RDP open to the internet | posture.network.admin_ports | No enabled Cloud Firewall that protects a Linode lets TCP port 22 or 3389 in from 0.0.0.0/0 or ::/0. Inbound rules apply in order, the first matching rule decides, and traffic no rule matches meets the firewall's inbound policy. |
| Linodes behind a Cloud Firewall | posture.network.firewall_coverage | Every Linode has an enabled Cloud Firewall, assigned to the Linode or to one of its interfaces. |
| Databases open to the internet | posture.network.databases | No managed database's access list holds 0.0.0.0/0 or ::/0. |
| Linode backups | posture.resilience.backups | Every Linode has the Backup service on. The detail says whether new Linodes get backups by default. |
| LKE control planes | posture.kubernetes.control_plane | Every LKE cluster has a high-availability control plane and an enabled control plane access list that does not admit every address. |
Linode reports each user's latest sign-in attempt only. When that attempt failed, the user's last use is unknown and Unused users leaves the user out. The vendor page lists the account's users with their access, two-factor authentication and latest successful sign-in.
Activity
Keen records Cloud Manager sign-ins as login, with the address they came from, and the account's events under their own action names, such as user_create, firewall_update or linode_boot, with the user who acted and the resource. Linode keeps both for 90 days. Each read stops 15 minutes before the present.
1. Create a read-only personal access token
- Sign in to Cloud Manager as an unrestricted user: Linode lists users and sign-ins only to unrestricted users.
- Open your profile menu, choose API Tokens → Create a Personal Access Token, name it, for example Keen posture, and choose an expiry.
- Set Select All to No Access, then set the scopes below to Read Only, and create the token. Copy it at once: Cloud Manager shows it only once.
| Scope | Cloud Manager name | Needed by |
|---|---|---|
account:read_only | Account | The account's name and ID, every user check, the backup default and sign-ins |
events:read_only | Events | Account events |
firewall:read_only | Firewalls | SSH and RDP open to the internet, and Linodes behind a Cloud Firewall |
linodes:read_only | Linodes | Linodes behind a Cloud Firewall, and Linode backups |
databases:read_only | Databases | Databases open to the internet |
lke:read_only | Kubernetes | LKE control planes |
2. Configure Keen
| Setting | Purpose |
|---|---|
KEEN_LINODE_ENABLED | Turns Akamai Cloud posture on. |
LINODE_TOKEN | The token from step 1. |
3. Verify, rotate or revoke
Recreate the API, worker and beat containers and choose Admin → Ingest runners → Run Akamai Cloud (Linode), then open the Akamai (Linode) vendor's Cloud posture tab. A check that reads Not established names its reason: not allowed means a scope is missing or the token belongs to a restricted user; not set up, or the credentials were not accepted covers a missing, expired or revoked token. Before the token expires, create another, update LINODE_TOKEN, recreate the containers and revoke the old token under API Tokens.