Analytics & Reporting
Relevant source files
The following files were used as context for generating this wiki page:
The Analytics & Reporting system in Fixops provides a comprehensive framework for visualizing security posture, calculating business impact, and generating executive-level insights. It bridges the gap between raw technical findings—such as SARIF outputs and SBOM inventories—and high-level business decisions by applying multi-LLM consensus, financial risk quantification, and compliance mapping.
This module is responsible for orchestrating data from various scanners (SAST, DAST, CNAPP), enriching it with threat intelligence (KEV, EPSS), and presenting it through specialized dashboards and scheduled reports. It serves as the primary "Command & Control" interface for Enterprise DevSecOps operations, enabling teams to track metrics like Mean Time to Remediate (MTTR), consensus rates, and audit compliance.
System Architecture and Data Flow
The reporting and analytics pipeline follows a multi-stage flow from ingestion to decision visualization. Data is ingested via CLI or API, processed through an enrichment layer, and then aggregated into specialized analytics models.
The diagram shows the end-to-end flow from raw scanner data to final executive insights and scheduled reports.
Sources: frontend/src/pages/EnhancedDashboard.jsx:215-228, fixops-enterprise/src/services/advanced_pentest_engine.py:915-945
Analytics Engine
The Analytics Engine processes security findings to generate high-level metrics and trends. It focuses on noise reduction, risk scoring, and ROI calculation for security operations.
Key Analytics Components
- Consensus Metrics: Tracks the agreement rate across multiple AI models (GPT-4, Claude, Gemini) during vulnerability analysis.
- Risk Quantification: Calculates an overall risk score (0-100) based on severity weights, asset criticality, and data classification.
- ROI Calculator: Estimates cost avoidance based on prevented security incidents ($15K average per incident) and developer time saved.
Sources: frontend/src/pages/EnhancedDashboard.jsx:100-115, 545-560, fixops-enterprise/src/services/advanced_pentest_engine.py:755-780
Analytics API Endpoints
| Endpoint | Method | Description |
|---|---|---|
/api/v1/analytics/dashboard/overview | GET | High-level system health and security posture. |
/api/v1/analytics/findings | GET | Aggregated counts and details of security findings. |
/api/v1/analytics/mttr | GET | Metrics for Mean Time to Remediate vulnerabilities. |
/api/v1/analytics/roi | GET | Financial metrics and cost avoidance data. |
/api/v1/analytics/decisions | GET | History of ALLOW/BLOCK/DEFER decisions. |
Sources: tests/e2e/comprehensive_e2e_test.py:850-865, CLI_API_INVENTORY.md:120-130
Reporting Framework
The reporting system allows users to generate, schedule, and distribute technical and executive reports in multiple formats, including PDF, HTML, JSON, and SARIF.
Report Types
- Executive Summary: High-level metrics, risk trends, and financial impact for leadership.
- Compliance Audit: Detailed mapping of findings to frameworks like SOC2, ISO27001, HIPAA, and PCI-DSS.
- Technical Detail: Deep-dive findings including remediation code snippets and MITRE ATT&CK mapping.
- Team Performance: Operational metrics focusing on remediation velocity and SLA compliance.
Sources: web/apps/reports/app/page.tsx:15-80, fixops-enterprise/src/services/advanced_pentest_engine.py:950-975
Data Structures for Reporting
@dataclass
class ExecutiveDashboard:
generated_at: datetime
overall_risk_score: float # 0-100
risk_trend: str # improving, stable, degrading
critical_findings: int
high_findings: int
total_findings: int
total_financial_risk_usd: float
compliance_scores: Dict[str, float]
Sources: fixops-enterprise/src/services/advanced_pentest_engine.py:305-325
Business Impact Quantification
A critical feature of the reporting system is the ability to translate technical vulnerabilities into financial terms. This engine uses industry benchmarks (e.g., IBM Cost of Data Breach) to estimate potential impact.
The sequence diagram illustrates how technical findings and business context are merged to produce financial risk estimates.
Sources: fixops-enterprise/src/services/advanced_pentest_engine.py:645-680, frontend/src/pages/EnhancedDashboard.jsx:580-600
Impact Factors
- Record Cost: Varies by data classification (e.g., $100 for Internal, $500 for Top Secret).
- Downtime Cost: Based on hourly revenue and asset criticality (Mission Critical vs. Development).
- Regulatory Fines: Estimates based on framework-specific rules (e.g., GDPR 4% revenue max).
Sources: fixops-enterprise/src/services/advanced_pentest_engine.py:615-640
Multi-LLM Consensus Reporting
For high-assurance environments, the system reports on the reasoning and confidence levels of different AI models. This "Disagreement Analysis" identifies areas where models like GPT-4 and Claude diverge, triggering expert review.
Consensus Metrics
- Confidence Variance: The spread of confidence scores across models.
- Decision Split: A boolean flag indicating if models disagree on the final action (ALLOW/BLOCK).
- Reasoning Snippets: Concise rationales from each model stored in the Evidence Lake for auditability.
Sources: frontend/src/pages/EnhancedDashboard.jsx:435-465, fixops-enterprise/src/services/advanced_pentest_engine.py:530-560
Conclusion
The Analytics & Reporting module transforms Fixops from a scanning tool into a decision-support system. By quantifying technical debt in financial terms and leveraging multi-LLM consensus for high-fidelity decisions, it provides both developers and executives with the specific evidence needed to prioritize remediation and maintain compliance across complex enterprise architectures.