# SolrSunrise Security Posture

SolrSunrise is built for authorized defensive security monitoring, exposure management, vulnerability prioritization, evidence handling, and remediation workflow.

## Authorized scope
SolrSunrise should be used only for assets, domains, cloud surfaces, applications, and infrastructure where the customer or operator has authorization to monitor, scan, review, or coordinate remediation.

## Defensive use
The platform direction is defensive and operational: discover exposed risk, prioritize known signals, preserve evidence, assign owners, request retests, and track closure. It is not positioned as breach glamor, unauthorized testing, or a guarantee that systems are secure.

## Evidence handling
Exposure findings, screenshots, hostnames, IP addresses, request/response evidence, remediation notes, ownership records, and reports can be sensitive operational security records. SolrSunrise treats these records as customer security data that should be scoped, role-controlled, retained intentionally, and reviewed by humans for high-impact decisions.

## Tenant and role boundaries
For MSSPs and multi-account operations, SolrSunrise is designed around tenant separation, role-based access, provider/client boundaries, technician work queues, account ownership, and client-facing reports.

## Human review
SolrSunrise supports prioritization and workflow, but security teams remain responsible for confirming scope, validating findings, coordinating maintenance windows, approving remediation, and making legal/compliance decisions.

## Trust language
SolrSunrise avoids unsupported claims such as breach prevention guarantees, military-grade promises, fake SOC metrics, fake customer logos, or unverified compliance claims.