Authorization before depth
Assessment depth is bound to website ownership, explicit permission and exact target scope.
LumicSec
Loading secure workspace…
Trust Center
LumicSec explains how authorization, evidence, customer data and human access are handled so teams can evaluate the operating model before using the product.
Assessment depth is bound to website ownership, explicit permission and exact target scope.
Representative evidence and reliability rules control customer-facing conclusions.
Workflow actions and finding disappearance are not proof that a condition is fixed.
Operating controls
These statements describe the current product operating model. LumicSec does not imply SOC 2, ISO or other certification unless such certification is actually obtained and published.
LumicSec customer assessment workflows are designed to avoid brute force, password guessing, login bypass, destructive exploitation, denial-of-service behavior and uncontrolled mutation.
Standard and Authenticated Security Assessments remain separate trust boundaries. Deeper application workflows require verified ownership or explicit authorization and target-scoped controls.
Customer evidence stays tenant-bound. The product is designed to retain only the evidence needed for assessment, remediation, reporting and retest-comparison workflows.
Human administrators are metadata-only by default for customer security evidence. Exceptional support access uses assessment-scoped, reasoned, short-lived and audited break-glass controls.
Potential LumicSec security issues can be reported through the published responsible-disclosure policy and security contact.
LumicSec relies on selected infrastructure and service providers for application hosting, data services and approved product operations. Provider use does not override customer authorization or evidence boundaries.
Policies
Policy 01
Open policy →
Policy 02
Open policy →
Policy 03
Open policy →
Policy 04
Open policy →
Policy 05
Open policy →
Policy 06
Open policy →
Policy 07
Open policy →
Policy 08
Open policy →
Policy 09
Open policy →