Where controls apply
5 sources planned · 3 liveWhich sources report on Production Cloud and what each one feeds. 2 connections need attention — together they block 9 controls.
◎Resume Okta setup →
Next step
Finish the Okta setup
Setup step 2 of 4 — finishing it unblocks 6 controls. Fixing Azure Prod's credentials unblocks the other 3.
Sources on this scope
Live sources3 live · feeding the 412 covered controlshealthy
☁Live· 99 of 142 workloads covered
Production AWS
AWS · 142 workloads
▢Live
vSphere DC-East
VMware · 38 hosts
⑂Live
GitHub org
GitHub · 24 repos
Of the 412 covered controls, AWS feeds 268 · vSphere feeds 141 · GitHub feeds 96 — most controls draw on more than one source, so these overlap and total more than 412.
Needs attentionblocking 9 controls — 6 Okta + 3 Azure9 blocked controls
◎Setup step 2 of 4 — Resume →
Okta
Identity · SSO · no inventory yet
◇Credentials failing — Fix →
Azure Prod
Azure · 76 workloads
Neither renders a coverage bar or an affirmative dot — only live sources report measured coverage. Unblock counts are not additive across alternative sources: Okta and Microsoft Entra ID address the same 6 controls, so connecting either clears them.