
Security Incident Response Automated Simulations (SIRAS) are internal events that provide a structured opportunity to practice the incident response plan and procedures during a realistic scenario. The system is currently available for AWS, but it is to be extended to others cloud platforms.
SIRAS v3.0 is a modern Security Incident Response Automated Simulation framework designed to manage red teaming exercises as code. You can execute controlled security simulations that test your Incident Response plan in realistic scenarios.
The main goal of SIRAS is to provide red teaming exercises as code, generating simulations against attack scenarios and highlighting possible failures in your incident response plan. The tests are called Smokers, each one executing real security actions and then cleaning up the resources created during execution.
The system is currently available for AWS and General providers, with a modular architecture that allows easy extension to other cloud platforms.

git clone https://github.com/stuxend/siras
cd siras
pip install -r requirements.txt
SIRAS v3.0 introduces a modern CLI interface with improved user experience:
# List all providers
python -m siras list-providers
# List smokers for a specific provider
python -m siras list-smokers aws
python -m siras list-smokers general
# Run an AWS smoker
python -m siras run aws open_security_group
# Run with options
python -m siras run aws s3_public --verbose --timeout 600
# Run all AWS smokers sequentially
python -m siras run-all aws
# Run all AWS smokers in parallel
python -m siras run-all aws --parallel --max-workers 3
docker run --rm \
-e AWS_ACCESS_KEY_ID \
-e AWS_SECRET_ACCESS_KEY \
-e AWS_SESSION_TOKEN \
-e AWS_DEFAULT_REGION=us-east-1 \
sochub/siras:latest run aws s3_public
| Smoker | Description |
|---|---|
| open_security_group | Creates an open security group with permissive rules |
| s3_public | Creates a public S3 bucket to test access controls |
| threat_intelligence | Tests threat intelligence detection capabilities |
| Smoker | Description |
|---|---|
| test_logger | Tests logging and monitoring systems |
requirements.txt for full dependenciesWe welcome all contributions, suggestions, and feedback, so please do not hesitate to reach out.
Ways you can contribute:
This project adheres to the Linux Foundation Code of Conduct available on the event page. By participating, you are expected to honor this code.