IDSENTRACustomer security architecture
See where identity context enters, where decisions happen and where protected records remain.
Focus on the customer environment: identity capture, protected operations, administration and approved integrations.
- 01Experience layer
- 02Identity services
- 03Policy engine
- 04Integration boundary
- 05Evidence layer
- 06Administration
Customer architecture
Four controlled zones around one operational record.
Each zone has one responsibility.
- EDGECapture
- EDGEProtected operations
- CONTROLAdministration
- CONTROLApproved connections
What the boundaries protect
Security follows the information and the authority to act on it.
- Access boundary
- Sensitive workflows stay limited to appropriately authorized users.
- Organization boundary
- Customer operational records remain scoped to the authorized environment.
- Integration boundary
- External systems receive only the access required by the approved workflow.
- Public boundary
- Protected operational payloads do not belong on public marketing surfaces.
Turn architecture into a launch plan
Validate the selected environment before production use.
Move from trust boundaries into ownership for users, sites, sources, devices, integrations, retention, recovery, testing and training.