ciscoconfaudit
Based on Use Cisco IOS XE Hardening Guide and some opinionated best practices.
This package gives an overview of the hardening techniques that can be used to secure a Cisco network device. Network security is not a one-layer thing, yet, it depends on multiple factors. If you harden your devices, then it is a good starting point that increases the overall security of the environment you manage.
Installation
Install from PyPi
$ pip install ciscoconfaudit
Usage
You can try out two examples in the repo in examples.
(.venv) $ python3 basic_online.py # Parses config from a device (Uses netmiko)
(.venv) $ python3 basic_offline.py # Parses config from text file
Example Output
| Global Config Audit (Sample) | Interface-Level Audit |
|---|---|
Use Case
- Ever been tired of checking whether the Cisco hardneing technqiues (here) are applied to your network devices one by one? This package is very handy in generating a tabular report for you.
Author
Credits
This package was inspired by jonarm from cisco-ios-audit.
Contributions
You are welcome to contribute to this Cisco Swiss army knife.
Metadata
Release files for ciscoconfaudit 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ciscoconfaudit-0.2.1.tar.gz | 47.5 kB | Without provenance | Details for ciscoconfaudit-0.2.1.tar.gz |
Release files / ciscoconfaudit-0.2.1.tar.gz
| Download URL | ciscoconfaudit-0.2.1.tar.gz |
|---|---|
| Size | 47.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1615341afb284a040551e6bfe4d4989e2caea91a5122e70253c1ca1106438eaa
|
|
BLAKE2b-256 checksum How to use checksums |
db25eb29826b400932e80d93382b2f44d47c7cff21863b1df528daaae7ccbd25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Security for ciscoconfaudit 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.