|
How is hardening checked?
|
By reviewing device settings manually against policy or best practice.
|
By probing services and known vulnerabilities from the network.
|
By analyzing exported router, switch and firewall configurations.
|
|
Can it validate configuration logic?
|
Yes, but reviews are slow, inconsistent and hard to scale.
|
Limited visibility into routing, segmentation and device-specific controls.
|
Analyzes the settings that control access, reachability, segmentation and trust.
|
|
Does it touch live devices?
|
Often requires engineer access, device checks and manual evidence gathering.
|
Yes, active scanning can generate traffic and noise.
|
No active probing; assessments use exported configurations.
|
|
Can teams prioritize fixes?
|
Prioritization depends on reviewer judgment and may vary by team.
|
Severity scores may not reflect configuration exposure or operational impact.
|
Prioritizes hardening gaps by exposure impact and device context.
|
|
Can hardening be proven?
|
Evidence is often spreadsheet-based or manually assembled.
|
Requires rescans or separate validation.
|
Reassess after changes and export evidence for audits, reviews and governance.
|
|
Does it map to compliance frameworks?
|
Mapping is manual and usually rebuilt for each audit cycle.
|
Findings map to CVEs rather than configuration controls.
|
Maps findings to CIS Benchmarks, NIST SP 800-53, NIST SP 800-171, PCI DSS 4.0, CMMC, RMF and DISA STIG, with pass or fail evidence per control. Framework-mapped reporting requires the Compliance tier of Nipper InfraSight.
|
|
Can it work in air-gapped or restricted environments?
|
Possible, but slow, inconsistent and hard to evidence at scale.
|
Often restricted or prohibited where active probing is not permitted.
|
Yes. The Air Gapped tier of Nipper InfraSight delivers the full capability set offline, for isolated, sovereign, classified and OT environments.
|