OktaOverview
You can grant users access to applications directly or through groups. The latter is preferred because it greatly simplifies access management.
Remediation guidance
Go to the Groups page, under the Directory section, in the Okta Admin Dashboard, select or create the group, and on the Applications tab, press Assign applications. Now, you can remove the individual user assignment. We recommend following the assignment conversion process described in the Okta documentation.
Service-wide remediation
Recommended when many resources are affected: fix the platform baseline first so new resources inherit the secure setting, then remediate the existing flagged resources in batches.
Okta
Use tenant-wide sign-on policies, MFA policies, admin-role governance, and identity lifecycle automation so the control is enforced centrally.
Operational rollout
- Fix the baseline first at the account, subscription, project, cluster, or tenant scope that owns this control.
- Remediate the currently affected resources in batches, starting with internet-exposed and production assets.
- Re-scan and track approved exceptions with an owner and expiry date.
Query logic
These are the stored checks tied to this control.
Application assignments are configured through groups
Connectors
Covered asset types
Expected check: eq []
users(where: { applicationsConnection_SOME: {edge: {scope_NOT: "GROUP"}}}) {...AssetFragment}
