Project Description
Gathers evidence, performs testing, and creates audit reports in ~25 lines of code per provider (AWS, GitHub, etc).
This project is maintained and published by AuditOps.io.
Use cases:
- Vendor Due Diligence: Evaluate your vendors actual security posture using transparent and timely reports.
- Audits: Automatically collect and share high quality evidence directly to your auditor (no screenshots required).
Getting Started (AWS Example)
- Install pre-requisites:
- Python Tutorial
- AWS CLI
- Run these commands to check if everything is installed correctly. If you receive an error, go back to the videos in Step 1.
python --version aws --version - Install the auditops library
pip install auditops - Create an IAM user (or Identity Center user) in the AWS management console.
- The user needs Security Audit permissions.
- Create an access key for the IAM user created in the previous step: AWS Docs
- NOTE: Configure the access key on your local machine using the 'aws configure' command Video Tutorial.
- NOTE: Access keys can only be viewed once, at the time of creation. They must be stored securely elsewhere for future use.
- Copy the code below and name the file auditops_example.py.
from auditops.core.models import Audit, AuditHelpers from auditops.providers.aws import AWSCollector, AWSTester, AWSConfig from auditops.core.utils import aws_create_session, run_audit def main(): session = aws_create_session() aws_config = AWSConfig(in_scope_regions=['us-east-1']) helpers = AuditHelpers.create() audit = Audit(helpers = helpers, title = "AWS Audit Report", config=aws_config, auditor_name = "AJ Dehn", evidence_folder = "aws") run_audit(audit, AWSCollector(session, audit), AWSTester(audit)) if __name__ == "__main__": main() - Run the code:
python auditops_example.py - The library will create a new 'tmp' folder containing audit_evidence and reports.
Design Philosophy:
- Lightweight: You can setup this library in minutes, and it doesn't require intensive integrations with your cloud providers. This eliminates vendor lock-in and gives you control over how your data is processed.
- Repeatability: Clear instructions explain how evidence was gathered and describes the test procedures that were performed. Share your AuditOps report + supporting evidence, and kindly ask your auditor to re-perform the work that was already done.
- Anti-Checkbox: We all know that compliance has become a check-box exercise. We hope you'll use this library to fight against it and start holding everyone to higher standard.
Metadata
Release files for auditops 0.1.5
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 | |
|---|---|---|---|---|
| auditops-0.1.5.tar.gz | 224.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auditops-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 471.4 kB
Release files / auditops-0.1.5.tar.gz
| Download URL | auditops-0.1.5.tar.gz |
|---|---|
| Size | 224.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
238b8bea941c96847b0498167b4fedf6ed3f9568c7c8f8df71cc2651f28d65f5
|
|
BLAKE2b-256 checksum How to use checksums |
518589a609fe2ebca501fcb9ffb58a387a06e496aa4cd65f14e76a3faae7691e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.1
|
Release files / auditops-0.1.5-py3-none-any.whl
| Download URL | auditops-0.1.5-py3-none-any.whl |
|---|---|
| Size | 247.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0462a2c208c69a8ea996a89eb96b39a0f93b2cee1ecc99a51f9f99fb33cb873c
|
|
BLAKE2b-256 checksum How to use checksums |
98a51cc1b856761d330d2706960d72eeddfa21175ae7060d2af152815fae06d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.1
|
Security for auditops 0.1.5
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.