Security Recommendations
Project-scoped GCP security posture: IAM least-privilege recommendations (Recommender API) plus service-account key hygiene — user-managed keys and disabled accounts.
What this pane shows
The security posture LightPane can read within a read-only project viewer, grouped by severity (CRITICAL / HIGH / MEDIUM / LOW) and category, with the description and remediation in the drawer:
- IAM recommendations — least-privilege suggestions from GCP's Recommender (roles that can be removed or replaced because the identity never uses them).
- Service-account key hygiene — service accounts holding user-managed keys (long-lived credentials that don't auto-rotate — GCP's most common credential-leak vector), flagged by age, plus disabled-but-present accounts.
This is the GCP counterpart to the AWS and Azure Security Findings panes. Note that GCP's Security Command Center — the organization-wide misconfiguration, vulnerability and threat feed — is org-scoped and needs the Premium/Enterprise tier, so it is not part of this project-scoped view; it is tracked for a later phase.
Key use cases
- Trim over-privileged identities down to least privilege.
- Find service accounts still using long-lived user-managed keys and rotate them onto Workload Identity Federation or short-lived credentials.
- Spot disabled service accounts that were never cleaned up.
- Review project IAM posture alongside the AWS and Azure security panes.
How often it refreshes
This pane refreshes every 30 min on every plan. Panes that draw on billing or recommendation APIs refresh on a per-plan schedule — see pricing.
Linking to LightPane
Once you connect one or more cloud accounts in LightPane you can create
access keys, which are what allow panes to read those
accounts. A key is a text string: the prefix lp_ak_ followed
by 43 characters drawn from A–Z a–z 0–9 - _
(URL-safe base64 of 32 random bytes), so 49 characters in all.
Each cloud account you connect is also given an account
handle — a short name such as zesty-ridge, minted
by LightPane when you link the account and never changed afterwards. It
lets a pane reference the same account for good, without putting a cloud
account ID in your page. Use the handle, not the account's editable
alias: renaming an alias makes a pane match nothing, and that failure is
silent — the pane shows an ordinary empty state, not an error.
More on naming accounts.
When adding the code below into your web page, replace
lp_ak_YOUR_ACCESS_KEY and YOUR_ACCOUNT_HANDLE
with your own access key and account handle.
- No key? Paste this exactly as it is. With the placeholder still in, the pane renders clearly-marked mock data, so you can place and style it before you connect anything. (A key that is present but rejected shows an error instead — a live dashboard must never quietly fall back to sample numbers.)
- No handle? The pane falls back to the access key's default account. That works, but the default moves if the key's grants change — naming a handle is what guarantees the same account every time.