README

Comprehensive system-level security monitoring for Laravel applications, integrating malware protection, runtime behavioral analysis, vulnerability detection, intrusion prevention, and firewall management.

Overview

Laravel Perimeter provides comprehensive security monitoring at the infrastructure boundary by seamlessly integrating multiple industry-standard security tools into a unified package with Laravel-native interfaces, standardized APIs, and consolidated logging. It creates a multi-layered security perimeter around your application to detect and respond to various security threats.

Core Components

1. File Protection (ClamAV Integration)

Malware scanning with OnAccess real-time protection
Scheduled and on-demand scanning with configurable paths
Signature-based detection with automatic database updates
Integration with Laravel's file upload system
Configurable exclusion patterns for performance optimization

2. Runtime Protection (Falco Integration)

Behavioral anomaly detection with kernel-level monitoring
Container runtime security for containerized environments
Suspicious process execution monitoring
File access anomaly detection
Network activity monitoring and alerting
Custom security rules for Laravel-specific threats
Point-in-time or continuous real-time monitoring modes

3. Vulnerability Scanning (Trivy Integration)

Full system vulnerability scanning of OS packages and system libraries (debian, ubuntu, alpine, etc.)
PHP dependency vulnerability detection (composer.lock)
JavaScript dependency scanning (package-lock.json, yarn.lock)
Known CVE detection with CVSS scoring
Configurable severity thresholds (CRITICAL, HIGH, MEDIUM, LOW)
License compliance checking
Configuration file security analysis
Container image scanning support

4. Intrusion Prevention (Fail2ban Integration)

Automatic detection and blocking of suspicious IPs
Protection for SSH, web applications, and API endpoints
Custom jail configurations for Laravel-specific attack patterns
Ban action monitoring and management
Integration with system firewall rules

5. Firewall Management (UFW Integration)

Network-level protection with simplified rule management
Service-based security policies
Port access control and monitoring
Policy enforcement and validation

6. Laravel Integration

File upload protection via middleware
Security event broadcasting
Integration with Laravel's logging system
Compatible with Laravel scheduler for automated scanning
Unified interfaces for all security components

7. Reporting & Data Export

Comprehensive security event collection and standardization
Raw security event data export (JSON/CSV)
Time-range filtering with from/to date parameters
Event type filtering (malware, vulnerability, behavioral)
Severity threshold filtering (critical, high, medium, low)
Configurable output formats (text, json, csv)
Security status overview for compliance documentation

Installation

1. Install the Package

composer require prahsys/laravel-perimeter

2. Publish the Configuration

php artisan vendor:publish --tag=perimeter-config

This will create a config/perimeter.php file in your application.

3. Run the Installation Command

This command will help you install and configure the required system dependencies:

# Complete installation (requires sudo/root privileges)
sudo php artisan perimeter:install

# Individual component installation is also available
php artisan perimeter:install-clamav    # Malware protection
php artisan perimeter:install-falco     # Runtime monitoring
php artisan perimeter:install-trivy     # Vulnerability scanning
php artisan perimeter:install-fail2ban  # Intrusion prevention
php artisan perimeter:install-ufw       # Firewall management

Each service is installed with optimized configurations for Laravel applications:

ClamAV: Installs with real-time protection capabilities and optimized scan settings
Falco: Installed without a kernel driver for non-interactive installation, providing comprehensive runtime monitoring with minimal system impact
Trivy: Configured for comprehensive system and dependency scanning with automated vulnerability database updates
Fail2ban: Set up with Laravel-specific jail configurations for web application protection
UFW: Configured with secure default policies and Laravel-friendly port rules

The installation command will:

Install the necessary security tools based on your system type
Configure each service for optimal operation with Laravel
Set up your .env file with appropriate Perimeter settings
Create necessary directories for rules and custom configurations
Set appropriate permissions for security operations

4. Configure Environment Variables

The installer will add these to your .env file, but you can customize them:

# Core configuration
PERIMETER_ENABLED=true
PERIMETER_LOG_CHANNELS=stack

# Service enablement
PERIMETER_CLAMAV_ENABLED=true
PERIMETER_FALCO_ENABLED=true
PERIMETER_TRIVY_ENABLED=true
PERIMETER_FAIL2BAN_ENABLED=true
PERIMETER_UFW_ENABLED=true

# Feature flags
PERIMETER_REALTIME_SCAN=true
PERIMETER_UPLOAD_PROTECTION=true

Basic Usage

1. Protect File Uploads

Add the Perimeter middleware to routes that handle file uploads:

// routes/web.php or routes/api.php
Route::middleware(['perimeter.protect'])->group(function () {
    Route::post('/upload', [UploadController::class, 'store']);
});

The middleware will:

Scan uploaded files for malware
Block files with detected threats
Log security events for audit purposes
Apply configurable threat response policies

2. Scan Files Programmatically

use Prahsys\Perimeter\Facades\Perimeter;

public function upload(Request $request)
{
    $file = $request->file('document');
    
    $scan = Perimeter::scan($file);
    if ($scan->hasThreat()) {
        return response()->json([
            'error' => 'Security threat detected: ' . $scan->getThreat()
        ], 422);
    }
    
    // Process safe file...
}

3. Schedule Regular Security Checks

Add these to your app/Console/Kernel.php file:

protected function schedule(Schedule $schedule)
{
    // Daily comprehensive security audit
    $schedule->command('perimeter:audit')->daily();
    
    // Weekly vulnerability scan with specific focus
    $schedule->command('perimeter:report --type=vulnerability')->weekly();
    
    // Weekly security health verification
    $schedule->command('perimeter:health')->weekly();
}

4. Set Up Real-time Monitoring

Perimeter provides comprehensive real-time security monitoring through two primary services:

Behavioral Monitoring with Falco

Falco provides kernel-level behavioral analysis to detect suspicious activities:

# Start behavioral monitoring
php artisan perimeter:monitor --services=falco

# Or run as a system service
sudo systemctl enable falco
sudo systemctl start falco

Falco monitoring provides:

Kernel-level visibility into all system calls
Rule-based detection of suspicious processes
Detection of privilege escalation attempts
Monitoring of file access patterns for data exfiltration
Network connection monitoring
JSON-formatted, standardized security events

Malware Detection with ClamAV

ClamAV provides real-time file system monitoring for malware:

# Enable malware monitoring
php artisan perimeter:monitor --services=clamav

ClamAV monitoring provides:

Real-time scanning of files as they are accessed
Detection of malware, trojans, and other threats
On-access protection for uploads and other file operations
Signature-based detection with daily database updates
Low false-positive rate suitable for web applications

Centralized Monitoring Dashboard

For continuous monitoring, use Supervisor:

[program:perimeter-monitor]
command=php /path/to/your/artisan perimeter:monitor
autostart=true
autorestart=true
user=www-data
redirect_stderr=true
stdout_logfile=/var/log/perimeter-monitor.log

The combined monitoring system:

Stores all security events in a standardized format
Provides audit-ready logs for compliance requirements
Timestamps and categorizes all security events
Associates events with specific scans for traceability
Tracks service origin for each event (falco, clamav, etc.)
Enables filtering by severity, type, and timeframe

5. Respond to Security Events

// Register custom event handlers
use Prahsys\Perimeter\Facades\Perimeter;
use App\Notifications\SecurityAlertNotification;

// In your service provider
Perimeter::onThreatDetected(function ($securityEvent) {
    // Notify security team via Slack
    Notification::route('slack', config('security.slack_webhook'))
        ->notify(new SecurityAlertNotification($securityEvent));
    
    // Log to specialized security log
    Log::channel('security')->critical('Security threat detected', [
        'event' => $securityEvent->toArray()
    ]);
});

Command Reference

Security Audit

Perform a comprehensive security assessment across all protection layers:

# Run audit on all enabled services
php artisan perimeter:audit

# Run audit only on specific services
php artisan perimeter:audit --services=clamav,trivy
php artisan perimeter:audit --services=ufw

# Combine with other options
php artisan perimeter:audit --services=clamav,falco --format=json

This command:

Checks all security components for proper operation
Scans the application for malware
Scans system packages and dependencies for vulnerabilities
Analyzes recent behavioral events
Checks firewall and intrusion prevention status
Generates a comprehensive security assessment

Options:

--format=json - Output in JSON format for automated processing
--services=clamav,trivy - Run audit only for specific services (comma-separated)

Health Check

Verify that all security components are properly installed and operational:

php artisan perimeter:health

This command quickly verifies:

Service installation status
Service configuration status
Service operational status
Environment configuration
Required permissions

Monitoring

Monitor security events across all protection layers:

# Point-in-time check of recent security events
php artisan perimeter:monitor

# Continuous monitoring
php artisan perimeter:monitor

# Service-specific monitoring
php artisan perimeter:monitor --services=falco

Options:

--duration=3600 - Duration in seconds (default: indefinite)
--services=clamav,falco - Focus on specific security services (comma-separated)

Reporting

Generate detailed security reports with flexible filtering:

php artisan perimeter:report

Options:

--scan-id=123 - Filter by specific scan ID
--from=2025-01-01 - Start date for filtering events
--to=2025-06-01 - End date for filtering events
--type=malware,vulnerability,behavioral - Filter by event type
--severity=critical,high,medium,low - Filter by severity
--format=json - Output format (text, json, csv)
--output=/path/to/file.json - Output file path
--scans-only - Show only scan summary without event details

System Maintenance

# Prune old security events and scan records
php artisan perimeter:prune

# Maintain security databases (ClamAV signatures, Trivy vulnerabilities)
php artisan perimeter:update-databases

Audit Artifacts

Laravel Perimeter automatically collects comprehensive audit artifacts during security audits, providing detailed compliance documentation and forensic evidence.

What Are Audit Artifacts?

Audit artifacts are timestamped collections of security service outputs, logs, and system states captured during each security audit. These artifacts serve multiple purposes:

Compliance Documentation: Detailed records for security audits and compliance reporting
Forensic Evidence: Preserved system states and security tool outputs for incident investigation
Historical Analysis: Point-in-time snapshots of security posture for trend analysis
Troubleshooting: Detailed service outputs to diagnose security tool issues

Artifact Collection

Every time you run php artisan perimeter:audit, the system automatically:

Captures Service Outputs: Collects logs, scan results, and status information from all enabled security services
Records System State: Documents firewall rules, service configurations, and system health
Generates Metadata: Creates audit summaries with timestamps, service versions, and scan statistics
Compresses Archives: Packages all artifacts into timestamped ZIP files for efficient storage

Example artifacts include:

ClamAV scan logs and malware detection reports
Trivy vulnerability scan results and database information
UFW firewall status and rule configurations
Fail2ban intrusion logs and banned IP lists
Falco behavioral monitoring events
Complete audit command output (audit.log)

Storage Configuration

Configure artifact storage in config/perimeter.php:

'artifacts' => [
    'disk' => env('PERIMETER_ARTIFACTS_DISK', 'local'),
    'root_path' => env('PERIMETER_ARTIFACTS_ROOT_PATH', 'perimeter/audits'),
    'retention_days' => env('PERIMETER_ARTIFACTS_RETENTION', 90),
],

Storage Disk Options

Use any Laravel storage disk for artifact storage:

// Local storage (default)
'disk' => 'local'

// AWS S3 for distributed environments
'disk' => 's3'

// Custom disk for shared storage
'disk' => 'audit_storage'

Environment Variables

# Storage configuration
PERIMETER_ARTIFACTS_DISK=s3
PERIMETER_ARTIFACTS_ROOT_PATH=compliance/security-audits
PERIMETER_ARTIFACTS_RETENTION=365

Distributed Environments

For server clusters or distributed deployments, you can add machine identification to artifact paths to prevent conflicts:

Option 1: Machine ID in Path

# Add server identifier to artifact path using hostname
PERIMETER_ARTIFACTS_ROOT_PATH=perimeter/audits/${HOSTNAME}
# Results in: perimeter/audits/web-server-01/2025-06-26/...

# Or use a custom environment variable you define
MACHINE_ID=prod-web-001
PERIMETER_ARTIFACTS_ROOT_PATH=perimeter/audits/${MACHINE_ID}
# Results in: perimeter/audits/prod-web-001/2025-06-26/...

Option 2: Custom Disk Per Environment

// config/filesystems.php
'audit_storage' => [
    'driver' => 's3',
    'key' => env('AWS_ACCESS_KEY_ID'),
    'secret' => env('AWS_SECRET_ACCESS_KEY'),
    'region' => env('AWS_DEFAULT_REGION'),
    'bucket' => env('AWS_BUCKET'),
    'root' => 'security-audits/' . env('SERVER_ID', gethostname()),
],

Option 3: Dynamic Path Configuration

// In a service provider
Config::set('perimeter.artifacts.root_path', 
    'perimeter/audits/' . env('CLUSTER_NODE_ID', gethostname())
);

Artifact Structure

Artifacts are organized in a consistent directory structure:

perimeter/audits/
├── 2025-06-26/
│   └── 2025-06-26_14-30-15_abc123def/
│       ├── audit_summary.json       # Overall audit results
│       ├── audit_metadata.json      # Scan metadata and timing
│       ├── audit_log.txt            # Complete audit command output
│       ├── clamav_log.txt           # ClamAV scan results
│       ├── trivy_version.txt        # Trivy version and scan output
│       ├── ufw_status.txt           # UFW firewall status
│       └── ...
│   └── artifacts.zip               # Compressed archive
└── 2025-06-25/
    └── ...

Artifact Retention

Artifacts are automatically cleaned up based on the retention period:

# Manual cleanup of old artifacts
php artisan perimeter:prune

# Automatic cleanup (if enabled in scheduler)
$schedule->command('perimeter:prune')->weekly();

Accessing Artifacts

Access artifacts through Laravel's storage system:

use Illuminate\Support\Facades\Storage;

// List available audit dates
$auditDates = Storage::disk(config('perimeter.artifacts.disk'))
    ->directories(config('perimeter.artifacts.root_path'));

// Get artifacts for a specific date
$todayArtifacts = Storage::disk(config('perimeter.artifacts.disk'))
    ->files(config('perimeter.artifacts.root_path') . '/' . now()->format('Y-m-d'));

// Download an artifact file
$artifactContent = Storage::disk(config('perimeter.artifacts.disk'))
    ->get('perimeter/audits/2025-06-26/2025-06-26_14-30-15_abc123def.zip');

Compliance Integration

Artifacts are designed to support various compliance frameworks:

SOC 2: Regular security monitoring evidence
ISO 27001: Information security management documentation
PCI DSS: Security scanning and monitoring logs
HIPAA: Security safeguard documentation
Custom Audits: Comprehensive security posture evidence

The standardized format and automated collection ensure consistent, auditable security documentation.

Advanced Integration Features

1. Logging Integration

All security events use Laravel's logging system, enabling seamless integration with your existing logging infrastructure:

// Configure security alerts in config/logging.php:
'channels' => [
    // Send critical security alerts to Slack
    'slack' => [
        'driver' => 'slack',
        'url' => env('LOG_SLACK_WEBHOOK_URL'),
        'username' => 'Laravel Perimeter',
        'emoji' => ':shield:',
        'level' => 'critical', // Only critical and above go to Slack
    ],
    
    // Dedicated security log for compliance
    'security' => [
        'driver' => 'daily',
        'path' => storage_path('logs/security.log'),
        'level' => 'info', // Capture all security events
        'days' => 90, // Retain logs for compliance purposes
    ],
    
    // Specialized channel for malware detections
    'malware' => [
        'driver' => 'daily',
        'path' => storage_path('logs/malware.log'),
        'level' => 'notice',
    ],
]

2. Event Handling & Callbacks

// In your AppServiceProvider or dedicated SecurityServiceProvider
use Prahsys\Perimeter\Facades\Perimeter;

public function boot()
{
    // Handle malware detections
    Perimeter::onThreatDetected(function ($securityEvent) {
        // Notify security team
        SecurityTeam::notifyMalwareDetection($securityEvent);
        
        // Quarantine the file
        Storage::move(
            $securityEvent->location, 
            "quarantine/{$securityEvent->details['hash']}"
        );
    });
    
    // Handle vulnerability detections
    Perimeter::onVulnerabilityFound(function ($vulnerability) {
        // Create ticket in issue tracker
        Jira::createSecurityTicket([
            'title' => "Security vulnerability: {$vulnerability->description}",
            'severity' => $vulnerability->severity,
            'details' => $vulnerability->details,
        ]);
    });
    
    // Handle behavioral anomalies
    Perimeter::onAnomalyDetected(function ($anomaly) {
        // Log IP address for further investigation
        if (isset($anomaly->details['source_ip'])) {
            SuspiciousActivity::record($anomaly->details['source_ip']);
        }
    });
}

3. Programmatic Reporting

Generate security reports programmatically for integration with dashboards or compliance systems:

use Prahsys\Perimeter\Facades\Perimeter;

// Get raw security data with flexible filters
$events = Perimeter::report()
    ->from(now()->subMonth())
    ->to(now())
    ->severity(['critical', 'high'])
    ->type(['malware', 'vulnerability'])
    ->get();

// Generate formatted reports for auditors
$report = Perimeter::report()
    ->from($auditPeriodStart)
    ->to($auditPeriodEnd)
    ->format('csv')
    ->export();

// Generate JSON for API consumption
return Perimeter::report()
    ->from(request('start_date'))
    ->to(request('end_date'))
    ->type(request('event_types', []))
    ->format('json')
    ->get();

Data Storage & Integration

The package provides robust data storage and standardized data structures for security events, making it easy to integrate with existing monitoring and compliance systems.

Database Storage

Security events are stored in dedicated database tables with optimized schemas:

perimeter_security_events: Stores standardized security events from all sources
- Includes type, severity, timestamps, descriptions, and structured details
- Supports JSON column for flexible event-specific data
- Indexed for efficient querying and reporting
perimeter_security_scans: Stores metadata about security scan operations
- Tracks scan types, timestamps, durations, and results
- Links to related security events
- Provides audit trail of security operations

The package automatically migrates these tables during installation.

Data Transfer Objects

All security events use standardized Data Transfer Objects (DTOs) that provide consistent representations across different security tools:

use Prahsys\Perimeter\Data\SecurityEventData;

// Create from malware scan results
$eventData = SecurityEventData::fromMalwareScan([
    'timestamp' => now(),
    'severity' => 'critical',
    'threat' => 'malware-signature',
    'file' => '/path/to/file.php',
    'hash' => 'sha256:1234...',
]);

// Create from behavioral analysis
$eventData = SecurityEventData::fromBehavioralAnalysis([
    'rule' => 'privilege_escalation',
    'priority' => 'critical',
    'description' => 'Suspicious activity detected',
    'process' => 'php',
    'user' => 'www-data',
]);

// Create from vulnerability scan
$eventData = SecurityEventData::fromVulnerabilityScan([
    'package' => 'vulnerable/package',
    'version' => '1.2.3',
    'cve' => 'CVE-2025-1234',
    'severity' => 'high',
    'description' => 'Remote code execution vulnerability',
]);

Security Assessment

The package provides detailed security assessments with actionable information through:

Comprehensive Issue Tracking: Clear categorization of issues by type and severity
Component Health Status: Verification that all security components are properly functioning
Protection Coverage: Assessment of which security layers are active and properly configured
Actionable Findings: Specific, concrete security issues that need attention
Compliance Information: Relevant data points for security compliance requirements

This detailed approach provides security professionals with clear, actionable insights about your application's security posture.

Example of security assessment output:

Security Assessment Summary
===========================
Components: 5 of 5 operational
Critical Issues: 0
High Issues: 2 (1 vulnerability, 1 suspicious behavior)
Medium Issues: 3 (all configuration related)
Low Issues: 1 (outdated security database)

Recent Activity
--------------
• Last scan: 2025-06-18 19:00:00
• Security events in last 24h: 3 (all medium severity)
• Most recent event: "Suspicious login attempt" (2025-06-18 18:45:12)

Required Actions
--------------
• Upgrade package "vulnerable/package" to version 2.0.1
• Review suspicious access to /etc/passwd by www-data user
• Configure fail2ban to protect Laravel login endpoints

Development Environment

Using Docker for Development

The package includes a Docker environment for local development and testing. This setup allows you to develop and test all security features without needing a full VM or physical machine.

Docker Setup Instructions

Make sure Docker and Docker Compose are installed on your machine
Run the following commands:

# Build and start the Docker environment
docker-compose up -d

# Check that the package is properly installed
docker-compose exec app php artisan list | grep perimeter

# Check status of security services
docker-compose exec app php artisan perimeter:health

# Run the package's tests
docker-compose exec app cd /package && composer test

This Docker configuration:

Creates a fully configured Laravel application for testing
Installs this package from the local directory with proper volume mounting
Properly configures all security components
Sets up necessary permissions and directory structures
Uses SQLite for a lightweight database with minimal configuration
Exposes the application on port 8000 for browser testing

How Security Services Run in Docker

The security services (ClamAV, Falco, Fail2ban, Trivy, UFW) are configured to work properly in the container with standard configurations and include:

Proper service startup and monitoring
Configuration management
Log collection and rotation
Full functionality testing
Status checking and reporting

This approach enables reliable testing across different environments with consistent behavior.

Testing Security Services

The Docker environment allows for comprehensive testing of all security components:

# Check health status of all components
docker-compose exec app php artisan perimeter:health

# Run a security audit
docker-compose exec app php artisan perimeter:audit

# Test monitoring (will run for 60 seconds)
docker-compose exec app php artisan perimeter:monitor --duration=60

# Generate a security report
docker-compose exec app php artisan perimeter:report

# Check individual service logs
docker-compose exec app cat /var/log/clamav/daemon.log
docker-compose exec app cat /var/log/fail2ban/daemon.log
docker-compose exec app cat /var/log/falco/daemon.log

# Check supervisor status
docker-compose exec app supervisorctl status

Troubleshooting

If you encounter issues during installation or operation, follow these steps:

1. Check Component Health

The first step is to verify all components are properly installed and configured:

php artisan perimeter:health

This provides a detailed status report of all security components with specific error messages.

2. Check Logs

Review the Laravel and component-specific logs:

# Laravel logs
tail -f storage/logs/laravel.log

# Component logs
tail -f /var/log/clamav/daemon.log
tail -f /var/log/fail2ban/daemon.log
tail -f /var/log/falco/daemon.log

3. Common Issues

Permission Problems: Security services often require elevated permissions. Ensure proper user/group settings.
Missing Dependencies: Some components require additional system packages. Check the installation output.
Container Limitations: Some features may be limited in containerized environments without privileged access.
Database Issues: Ensure migrations have run properly: php artisan migrate:status

4. ClamAV Not Starting

If you see "ClamAV is installed and configured but daemon is not running" in the health check:

# Check if freshclam has completed initializing the database
sudo systemctl status clamav-freshclam

# Check ClamAV logs for specific errors
sudo cat /var/log/clamav/freshclam.log
sudo cat /var/log/clamav/clamd.log

# Make sure required directories exist with proper permissions
sudo mkdir -p /var/run/clamav /var/lib/clamav
sudo chown clamav:clamav /var/run/clamav /var/lib/clamav
sudo chmod 750 /var/run/clamav /var/lib/clamav

# Manually start ClamAV services
sudo systemctl restart clamav-freshclam
sudo systemctl restart clamav-daemon

# Check socket file
ls -la /var/run/clamav/clamd.sock

See DEBUGGING.md for more detailed ClamAV troubleshooting steps.

5. Sample Outputs

The package includes reference outputs for all security tools in the resources/examples/ directory. These examples show what properly functioning services should produce and help with troubleshooting.

The resources/examples/perimeter/audit/ directory contains example audit artifacts showing the complete output structure of security audits, including service logs, scan results, and compliance documentation.

Documentation

For more detailed information, check out these documentation files:

RUNBOOKS.md - Incident response procedures and runbooks
DEBUGGING.md - Detailed debugging procedures for all components
Example outputs - Sample outputs from security tools

License

The MIT License (MIT). Please see License File for more information.

prahsys / laravel-perimeter

Maintainers

Details

README

Overview

Core Components

1. File Protection (ClamAV Integration)

2. Runtime Protection (Falco Integration)

3. Vulnerability Scanning (Trivy Integration)

4. Intrusion Prevention (Fail2ban Integration)

5. Firewall Management (UFW Integration)

6. Laravel Integration

7. Reporting & Data Export

Installation

1. Install the Package

2. Publish the Configuration

3. Run the Installation Command

4. Configure Environment Variables

Basic Usage

1. Protect File Uploads

2. Scan Files Programmatically

3. Schedule Regular Security Checks

4. Set Up Real-time Monitoring

Behavioral Monitoring with Falco

Malware Detection with ClamAV

Centralized Monitoring Dashboard

5. Respond to Security Events

Command Reference

Security Audit

Health Check

Monitoring

Reporting

System Maintenance

Audit Artifacts

What Are Audit Artifacts?

Artifact Collection

Storage Configuration

Storage Disk Options

Environment Variables

Distributed Environments

Option 1: Machine ID in Path

Option 2: Custom Disk Per Environment

Option 3: Dynamic Path Configuration

Artifact Structure

Artifact Retention

Accessing Artifacts

Compliance Integration

Advanced Integration Features

1. Logging Integration

2. Event Handling & Callbacks

3. Programmatic Reporting

Data Storage & Integration

Database Storage

Data Transfer Objects

Security Assessment

Development Environment

Using Docker for Development

Docker Setup Instructions

How Security Services Run in Docker

Testing Security Services

Troubleshooting

1. Check Component Health

2. Check Logs

3. Common Issues

4. ClamAV Not Starting

5. Sample Outputs

Documentation

License