Pull Request

Issue link(s):

Summary - What I changed

Adds a new rule for the first occurrence of an Okta public client app requested an OAuth token with client credentials from an unrecognized source.

Custom applications meant to interact with Okta's API can be registered in the admin console, where Oauth granting types can be specified. In this instance, a custom client application suspiciousApp was created and does not require DPoP, therefore tokens can be obtained by simply providing the client key and secret in any request to /oauth2/default/v1/token endpoint. Adversaries may gain access to these credentials via environment variables or other various discovery methods and then attempt to obtain an access token with unauthorized OAuth scopes.

Potential false-positives: Could occur from devs or testing where the incorrect scope was requested, however, repeat activity would not fire due to the new terms rule focusing on source ip (if someone uses a proxy during dev though, this would fire for sure). If this happens often, we could change the new terms field to the actual client application ID, indicating the first time this application had such as error because of compromised secrets

How To Test

Checklist

[x] Added a label for the type of pr: bug, enhancement, schema, Rule: New, Rule: Deprecation, Rule: Tuning, Hunt: New, or Hunt: Tuning so guidelines can be generated
[ ] Added the meta:rapid-merge label if planning to merge within 24 hours
[x] Secret and sensitive material has been managed correctly
[ ] Automated testing was updated or added to match the most common scenarios
[ ] Documentation and comments were added for features that require explanation

Contributor checklist

Have you signed the contributor license agreement?
Have you followed the contributor guidelines?

protectionsmachine commented 3 weeks ago

Rule: New - Guidelines

These guidelines serve as a reminder set of considerations when proposing a new rule.

Documentation and Context

[ ] Detailed description of the rule.
[ ] List any new fields required in ECS/data sources.
[ ] Link related issues or PRs.
[ ] Include references.

Rule Metadata Checks

[ ] creation_date matches the date of creation PR initially merged.
[ ] min_stack_version should support the widest stack versions.
[ ] name and description should be descriptive and not include typos.
[ ] query should be inclusive, not overly exclusive, considering performance for diverse environments. Non ecs fields should be added to non-ecs-schema.json if not available in an integration.
[ ] min_stack_comments and min_stack_version should be included if the rule is only compatible starting from a specific stack version.
[ ] index pattern should be neither too specific nor too vague, ensuring it accurately matches the relevant data stream (e.g., use logs-endpoint.process-* for process data).
[ ] integration should align with the index. If the integration is newly introduced, ensure the manifest, schemas, and new_rule.yaml template are updated.
[ ] setup should include the necessary steps to configure the integration.
[ ] note should include any additional information (e.g. Triage and analysis investigation guides, timeline templates).
[ ] tags should be relevant to the threat and align/added to the EXPECTED_RULE_TAGS in the definitions.py file.
[ ] threat, techniques, and subtechniques should map to ATT&CK always if possible.

New BBR Rules

[ ] building_block_type should be included if the rule is a building block and the rule should be located in the rules_building_block folder.
[ ] bypass_bbr_timing should be included if adding custom lookback timing to the rule.

Testing and Validation

[ ] Provide evidence of testing and detecting the expected threat.
[ ] Check for existence of coverage to prevent duplication.

terrancedejesus commented 3 weeks ago

@elastic/trade-admins - Can someone approve please.

elastic / detection-rules

[New Rule] Okta Public Client App OAuth Token Request with Client Credentials #4074