Security Findings
Consolidated Security Hub findings from Inspector, GuardDuty, Macie, IAM Access Analyzer and Config, prioritised by severity and filterable by source product.
What this pane shows
The consolidated finding feed Security Hub aggregates from its integrated products — Amazon Inspector (CVEs and network reachability), GuardDuty (threat detections), Macie (sensitive-data findings), IAM Access Analyzer (external access) and Config — normalised into one severity-prioritised list. Each finding shows its source product, affected resource, type, age and workflow state, with the full description and remediation in the drawer.
This is the counterpart to Security Compliance (Security Hub CSPM): that pane scores control pass/fail against standards like AWS Foundational Security Best Practices; this one is the actual product findings. Control findings are deliberately excluded here so the two never double-count.
Key use cases
- Daily triage of new high-severity findings across every security product at once.
- Filter to a single source (e.g. just Inspector CVEs, or just GuardDuty threats).
- Spot the highest-severity issues on an account without opening six consoles.
- Switch region to match the Security Hub view you're investigating.
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.