STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Okta Identity as a Service (IDaaS) Security Technical Implementation Guide

V-279689

CAT II (Medium)

Okta API tokens must be configured with Network Zones to restrict authorization from known networks.

Rule ID

SV-279689r1155066_rule

STIG

Okta Identity as a Service (IDaaS) Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-005165CCI-000366

Discussion

An access token is a piece of data that represents the authorization granted to a user or NPE to access specific systems or information resources. Access tokens enable controlled access to services and resources. Properly managing the lifecycle of access tokens, including their issuance, validation, and revocation, is crucial to maintaining confidentiality of data and systems. Restricting token validity to a specific audience, e.g., an application or security domain, and restricting token validity lifetimes are important practices. Access tokens are revoked or invalidated if they are compromised, lost, or are no longer needed to mitigate the risks associated with stolen or misused tokens. API tokens have the potential to be replicated or stolen (just like a password). Because of this, it is important to only allow API tokens to authenticate from known IP ranges as this limits an adversary's ability to use a token to gain access.

Check Content

From the Admin Console:

1. Select the "Security" menu, and then click the "API" item.
2. Click the "Tokens" tab.
3. For each token listed, click the token name link.
4. In the "Security" section, verify the "Token can be used from" setting is mapped to a known network zone for the application calling the API.

If a network zone for each API access token is not defined, this is a finding.

Fix Text

From the Admin Console:

1. Select the "Security" menu, and then click the "API" item.
2. Click the "Tokens" tab.
3. For each token listed, click the token name link.
4. In the "Security" section, click "Edit".
5. Set the "Token can be used from" setting to the known network zone for the application calling the API.
6. Click "Save".