mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 08:30:20 +00:00
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):
- brain/ LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
dispatch, A51 channels, and the OSINT cluster
- knowledge/ LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
MITRE ATT&CK data
- reference/ defensive threat-reference (C3, shhbruh doc) + AdaYaml parser
License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.
Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.
https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
79 lines
2.3 KiB
Markdown
79 lines
2.3 KiB
Markdown
---
|
|
name: analyzing-azure-activity-logs-for-threats
|
|
description: 'Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query to detect suspicious administrative
|
|
operations, impossible travel, privilege escalation, and resource modifications. Builds KQL queries for threat hunting in
|
|
Azure environments. Use when investigating suspicious Azure tenant activity or building cloud SIEM detections.
|
|
|
|
'
|
|
domain: cybersecurity
|
|
subdomain: security-operations
|
|
tags:
|
|
- analyzing
|
|
- azure
|
|
- activity
|
|
- logs
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- DE.CM-01
|
|
- RS.MA-01
|
|
- GV.OV-01
|
|
- DE.AE-02
|
|
---
|
|
|
|
# Analyzing Azure Activity Logs for Threats
|
|
|
|
|
|
## When to Use
|
|
|
|
- When investigating security incidents that require analyzing azure activity logs for threats
|
|
- When building detection rules or threat hunting queries for this domain
|
|
- When SOC analysts need structured procedures for this analysis type
|
|
- When validating security monitoring coverage for related attack techniques
|
|
|
|
## Prerequisites
|
|
|
|
- Familiarity with security operations concepts and tools
|
|
- Access to a test or lab environment for safe execution
|
|
- Python 3.8+ with required dependencies installed
|
|
- Appropriate authorization for any testing activities
|
|
|
|
## Instructions
|
|
|
|
Use azure-monitor-query to execute KQL queries against Azure Log Analytics workspaces,
|
|
detecting suspicious admin operations and sign-in anomalies.
|
|
|
|
```python
|
|
from azure.identity import DefaultAzureCredential
|
|
from azure.monitor.query import LogsQueryClient
|
|
from datetime import timedelta
|
|
|
|
credential = DefaultAzureCredential()
|
|
client = LogsQueryClient(credential)
|
|
|
|
response = client.query_workspace(
|
|
workspace_id="WORKSPACE_ID",
|
|
query="AzureActivity | where OperationNameValue has 'MICROSOFT.AUTHORIZATION/ROLEASSIGNMENTS/WRITE' | take 10",
|
|
timespan=timedelta(hours=24),
|
|
)
|
|
```
|
|
|
|
Key detection queries:
|
|
1. Role assignment changes (privilege escalation)
|
|
2. Resource group and subscription modifications
|
|
3. Key vault secret access from new IPs
|
|
4. Network security group rule changes
|
|
5. Conditional access policy modifications
|
|
|
|
## Examples
|
|
|
|
```python
|
|
# Detect new Global Admin role assignments
|
|
query = '''
|
|
AuditLogs
|
|
| where OperationName == "Add member to role"
|
|
| where TargetResources[0].modifiedProperties[0].newValue has "Global Administrator"
|
|
'''
|
|
```
|