Declared
An export shows the known state at a particular date.
Accounts and permissions can accumulate as circumstances change. We map a focused scope to support an access review, without promising a complete security audit.

Indicative starting budgets for the described scope, including applicable taxes for consumers. Total price and schedule are confirmed in a written quotation.
Scope this project ↗A role name does not explain every right it grants. The review compares intended use with declared permissions, separating matters to confirm from decisions actually made.
The pilot covers up to two applications and five roles. Using authorised exports or an accompanied demonstration, we prepare an access matrix and a list of differences to review. No permission is changed without a separate agreement.
The expected function is described before assigned rights are examined.
Reading, editing and administration remain distinct capabilities.
The application and affected resources are explicitly identified.
An export shows the known state at a particular date.
A difference raises a question, not an automatic deletion.
An authorised person approves a correction and any implementation.
Illustrative scenario: a read-only role is distinguished from administration. The displayed matrix is fictional and describes no real system.
Documentary analysis and recommendations only. Penetration testing, certification, password collection, exhaustive threat detection and automatic rights changes are excluded. Implementing corrections and any subscriptions are separate.
No. We prefer limited exports or an accompanied presentation. Never enter secrets into the public form.
No. It clarifies a defined scope and does not replace full risk analysis or appropriate security controls.
A few details are enough to start a useful conversation. No payment or commitment through the form.
Prepare my enquiry ↗