Infrastructure Security · IS-Q14B

Bonus Question: Are firewalls, routers, and switches configured with secure baselines and periodic rule reviews?

Why This Matters

Infrastructure devices must be hardened and reviewed regularly to prevent misconfigurations that attackers exploit. Secure baselines maintain consistency across environments.

Maturity

0 — Unaware
Default configurations used; no reviews performed.
1 — Ad Hoc
Manual configuration; no documented baseline.
2 — Defined
Baseline configuration established and approved.
3 — Managed
Periodic rule reviews and change logs maintained.
4 — Integrated
Automated compliance checks and configuration backups.
5 — Optimized
Continuous validation and real-time deviation alerts.

How to Level Up

| From → To | Actions | |—|—| | 0 → 1 |Harden all network devices; disable unused services.| | 1 → 2 |Document approved baseline templates.| | 2 → 3 |Perform quarterly rule and ACL reviews.| | 3 → 4 |Automate compliance checks and backups.| | 4 → 5 |Integrate alerts for unauthorized configuration changes.|

Enablers

Evidence

KPIs

Low-Cost / Open-Source Options (MSME)

| Purpose | Tool | Notes | |—|—|—| | Baseline backup | RANCID / Oxidized | Auto-archive configs | | Rule review | Nipper / FireFlow | Validate ACLs | | Compliance check | Lynis | Baseline hardening scans |

Common Pitfalls

Compliance Mapping

| Standard | Clauses / Notes | |—|—| | ISO/IEC 27001 | A.8.8 / A.8.23 | | CERT-In 2022 | Section 17 | | NIST CSF 2.0 | PR.PT / DE.CM | | NIRMATA Mapping | IS-Q14B enhances infrastructure hygiene via controlled and auditable configuration baselines. |