defense-hardening-baseline
Turn offensive findings into concrete hardening — the fix side of each vuln class, plus config baselines. Load for blue-team/remediation tasks, "how do we fix/prevent", secure config review, or writing the remediation section of a report. Signals: "harden", "remediation", "secure baseline", "prevent
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-hardening-baselineScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto8bf91c50…6301b2d4
8bf91c50966f…971f6301b2d41 file · 1.3 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-hardening-baseline@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When it applies
You need the defensive counterpart: how to fix a class of bug, or how to configure a system so the class can't occur. Pairs with every offensive skill's "why it works".
Why it works
Most vuln classes have a small set of correct, well-known mitigations. Applying the right control at the right layer (input handling, authz at the data layer, safe defaults) removes the class, not just the instance.
Remediation by class (the fix that actually works)
- Injection (SQLi/cmd/LDAP): parameterized queries / prepared statements; never build code from input; least-privilege DB users.
- XSS: context-aware output encoding + a strict CSP (nonce-based, no
unsafe-inline). - Access control (IDOR/BOLA): authorize at the object layer on every request; deny by default.
- SSRF: allowlist egress, block link-local/metadata, enforce IMDSv2, resolve+validate then pin.
- Deserialization: don't deserialize untrusted input; use data-only formats; allowlist types.
- Auth/JWT: verify signatures/alg, short expiry, rotate, MFA; secrets out of code/URLs.
- Upload: validate server-side by content, store outside webroot, random names, no exec.
- Secrets: vault/manager, scan CI, rotate on exposure.
Config baselines
- Cloud: CIS Benchmarks; scan with ScoutSuite/Prowler; enforce IMDSv2, block public buckets.
- Kubernetes:
kube-bench(CIS), least-privilege RBAC, no privileged pods, network policies. - Hosts: CIS baselines, patch cadence, disable unused services.
How to use
For a finding, cite the specific control here in the report's remediation, and (blue-team) turn
it into a config check or a detection (→ defense-detection-sigma).
References
OWASP Cheat Sheet Series; CIS Benchmarks; cloud provider security baselines.
File di questa versione
- SKILL.md2.3 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
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.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 8bf91c50 | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Linux, cloud e container
Vai alla categoria- 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login