Skip to content
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-hardening-baselineLinux, cloud and containers

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 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

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

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
Dh90qDHEu3…awrpUHAA==The CLI checks the SHA-256 and the signature before it writes a file.
Package8bf91c50…6301b2d4
8bf91c50966f…971f6301b2d41 file · ⁦1.3 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-hardening-baseline@ee0e0c5

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.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c58bf91c50Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login