nit IG format changes

Author: imays11

rules/integrations/aws/initial_access_iam_session_token_used_from_multiple_addresses.toml

@@ -35,7 +35,7 @@ note = """## Triage and Analysis
 
 Access tokens are bound to a single user. Usage from multiple IP addresses may indicate the token was stolen and used elsewhere. By correlating this with additional detection criteria like multiple user agents, different cities, and different networks, we can improve the fidelity of the rule and help to eliminate false positives associated with expected behavior, like dual-stack IPV4/IPV6 usage.
 
-#### Possible Investigation Steps
+#### Possible investigation steps
 
 - **Identify the IAM User**: Examine the `aws.cloudtrail.user_identity.arn` stored in `user_id` and correlate with the `source.ips` stored in `ip_list` and `unique_ips` count to determine how widely the token was used.
 - **Correlate Additional Detection Context**: Examine `activity_type` and `fidelity_score` to determine additional cities, networks or user agents associated with the token usage.
@@ -44,18 +44,18 @@ Access tokens are bound to a single user. Usage from multiple IP addresses may i
 - **Review Workload Context**: Confirm whether the user was expected to be active across multiple cities, networks or user agent environments.
 - **Trace Adversary Movement**: Pivot to related actions (e.g., `s3:ListBuckets`, `iam:ListUsers`, `sts:GetCallerIdentity`) to track further enumeration.
 
-### False Positive Analysis
+### False positive analysis
 
 - Automation frameworks that rotate through multiple IPs or cloud functions with dynamic egress IPs may cause this alert to fire.
 - Confirm geolocation and workload context before escalating.
 
-### Response and Remediation
+### Response and remediation
 
 - **Revoke the Token**: Disable or rotate the IAM credentials and invalidate the temporary session token.
 - **Audit the Environment**: Look for signs of lateral movement or data access during the token's validity.
 - **Strengthen Controls**: Require MFA for high-privilege actions, restrict access via policy conditions (e.g., IP range or device).
 
-### References
+### Additional information
 
 - [IAM Long-Term Credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html)
 - [STS Temporary Credentials](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html)
@@ -182,6 +182,11 @@ from logs-aws.cloudtrail* metadata _id, _version, _index
   Esql.data_stream_namespace_values
 
 | where Esql.activity_fidelity_score == "high"
+
+// this rule only alerts for "high" fidelity cases, to broaden the rule scope to include all activity
+// change the final condition to 
+// | where Esql.activity_type != "normal_activity"
+
 '''
 
 [rule.investigation_fields]