defense-cloud-detection
Detect and respond to attacks in cloud control planes — credential abuse, IMDS theft, persistence, and privilege escalation — from audit logs. Load for "detect cloud attacks", "CloudTrail/GuardDuty", "someone used our keys", AWS/Azure/GCP monitoring, or cloud IR. The defensive counterpart to the clo
v2026.10.14-ee0e0c53 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/defense-cloud-detectionEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete9f0189d0…6781564e
9f0189d0cb90…7cbb6781564e1 archivo · 1.6 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-cloud-detection@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
When it applies
Your assets live in AWS/Azure/GCP and you need to catch control-plane abuse — stolen keys, a role assumed from a strange place, new persistence — using the provider's audit logs.
Why it works
Every cloud API call is logged (CloudTrail / Azure Activity / GCP Admin Activity). Attacks that are invisible on the host (assuming a role, reading a secret, adding a key) are loud in the control plane — if you're actually reading it. The identity and the calling context are in every event.
Method
- Guarantee the telemetry: CloudTrail (all regions + management & data events), Azure Activity
- Entra sign-in logs, GCP audit logs — centralised and immutable. No logs → no detection.
- Credential-theft tells: an IAM user/role key used from a new ASN/region/UA, especially
sts:GetCallerIdentitythen enumeration bursts — classic stolen-key triage. IMDS-sourced role creds used off the instance (compare the session's source IP to the instance). - Persistence:
CreateAccessKey,CreateUser, new login profile,CreateRolewith a broad trust policy, new identity provider — alert on these in prod accounts. - Privilege escalation:
AttachUserPolicy/PutUserPolicygranting*,iam:PassRole+ service launch,AssumeRolechains that cross accounts. - Managed signals: enable GuardDuty / Defender for Cloud / SCC as a baseline, then tune and layer custom queries (Athena over CloudTrail) on top.
- Respond: disable the key/session, revoke role sessions, snapshot for forensics, rotate, and
review what the identity could reach (
tradecraft-attack-path-mapping).
Gotchas
- CloudTrail data events (S3 object-level, Lambda) are off by default — you miss exfil without them.
- Roles blur "who did it" — correlate the session name and source, not just the principal.
- Automation (CI/CD, Terraform) generates the same API calls; baseline service identities first.
Verify success
A simulated key-abuse / privilege-escalation sequence (e.g. via a lab) surfaces from the audit logs with the identity, source, and action, and the response revokes access and preserves evidence.
References
AWS CloudTrail & GuardDuty; Azure Monitor / Entra sign-in logs; GCP audit logs; MITRE ATT&CK Cloud matrix.
Archivos de esta versión
- SKILL.md2.9 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 9f0189d0 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Linux, cloud y contenedores
Ver la categoría- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- cloud-gcpnoorqureshi/cloud-gcp4
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login