Check security.Prove implementation.
SigXOS checks technical configurations against defined security rules and backs every finding with the configuration line it refers to.
Check run
Lab datarunning-configlines 11–15
- 11!
- 12enable secret 9 ••••••••••••
- 13no service password-encryption
- 14!
- 15ip ssh version 2
Password obfuscation enabled
- Evidence
- running-config, line 13
- Rule reference
- CIS-oriented
- Recommendation
service password-encryption
- F004SSH version 2 enforcedPassed
- F005Telnet disabled on VTY linesPassed
- F007Access list on VTY linesDeviation
- Read-only access
- No configuration changes
- Reproducible results
- In the pilot: local collection and storage
Solutions
Make security requirements testable
For security and network teams who need to know and prove the actual configuration state.
Configuration compliance
Check configurations repeatably against defined security rules instead of reviewing devices one by one.
Learn moreAudit and evidence preparation
Document every finding with configuration line, rule reference and time, ready for audits.
Learn moreCIS-oriented configuration checks
Check configurations against CIS-oriented rules and assess deviations by severity.
Learn moreRe-checks after changes
Check again after changes and keep the history of results traceable.
Learn more
Product
Collection, checks and evidence in one flow
The prototype works with Cisco IOS and IOS-XE as its first rule library. We add further vendors on request, with an individual timeline and plan.
- 22 CIS-oriented rules with severity
- Agentless, read-only collection via SSH
- Findings with configuration evidence
- Device inventory, audit trail and check report
How it works
How the check works
A repeatable process in four steps. Every finding stays traceable, even after changes.
1Collect
Collect configurations agentless and read-only. No software is installed on the devices.
2Check
Apply defined security rules to the collected state.
3Prove
Document every finding with the configuration line, rule reference and time.
4Re-check
Check again after changes and keep the history traceable.
Evidence, not assumptions
Every statement about the security state should trace back to the actual configuration.
More about our approachFrameworks
Frameworks and standards
The rules in the prototype are oriented on the CIS Benchmarks. Mappings to further frameworks are planned.
More on frameworks- CIS BenchmarksRule basis
- NIS-2 / BSIGPlanned
- BSI IT-GrundschutzPlanned
- ISO/IEC 27001Planned
- DORAPlanned
- PCI DSSPlanned
- NIST CSF 2.0Planned
- Internal policiesPlanned
Services
Start with a pilot
Together we find out whether SigXOS delivers the expected value in your environment.
Pilot programme
Paid design-partner pilot over 4–6 weeks, read-only in your environment.
Learn moreSet-up and review
Local, read-only collection, a joint review of the findings and a decision on next steps.
Learn morePartner programme
Planned offering for IT service providers and MSPs.
PlannedLearn more
Is SigXOS a fit for your environment?
You need to check and prove configurations regularly? Let’s find out in 30 minutes whether a pilot makes sense: directly with Cisco IOS/IOS-XE, with other vendors on an individual timeline and plan.