access management
2 articles with this tag
An organization's security minimum: six priorities worked back from Japan's 2026 breaches
An organization's 'minimum' should be set by where real incidents broke through, not by a product list. Line up Japan's 2026 incidents and the entry points differ — a VPN appliance, third-party software, a query feature, undisclosed — yet the causes that widened the damage come down to six: (1) close internet-facing devices on a deadline, (2) narrow maintenance, contractor and leaver accounts, (3) watch volume and time, (4) keep logs long enough to look back, (5) don't keep data you no longer need, (6) re-prioritise by KEV. This site's view: the minimum is deciding who notices, on which number, and when.
SSH key least privilege: keep production root keys off ephemeral environments that can be compromised
Registering a root key into production from an ephemeral, compromisable environment (GPU pod, CI runner, throwaway VM) means that the moment the environment is compromised, an attacker gets root on production. Fix: no root keys on ephemeral environments; remove keys when unused; if needed again, use a non-root user plus a command-restricted key that limits the key to one operation. Treat a reused key as your most critical asset, and never build a setup where one leaked key opens every server.