Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/defense-cloud-detectionLinux, cloud e container

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 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/defense-cloud-detection

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
uxRPJhiIQm…pzlYM6Bw==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto9f0189d0…6781564e
9f0189d0cb90…7cbb6781564e1 file · ⁦1.6 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-cloud-detection@ee0e0c5

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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

  1. 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.
  2. Credential-theft tells: an IAM user/role key used from a new ASN/region/UA, especially sts:GetCallerIdentity then enumeration bursts — classic stolen-key triage. IMDS-sourced role creds used off the instance (compare the session's source IP to the instance).
  3. Persistence: CreateAccessKey, CreateUser, new login profile, CreateRole with a broad trust policy, new identity provider — alert on these in prod accounts.
  4. Privilege escalation: AttachUserPolicy/PutUserPolicy granting *, iam:PassRole + service launch, AssumeRole chains that cross accounts.
  5. Managed signals: enable GuardDuty / Defender for Cloud / SCC as a baseline, then tune and layer custom queries (Athena over CloudTrail) on top.
  6. 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.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.10.14-ee0e0c513 nov 2026ee0e0c59f0189d0Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login