Security posture
Security Cockpit
Combine prioritized signals, source status and drill-down context in a role-specific security view.
IT security and governance
See the security posture. Understand risk. Make informed decisions.
CentaurNexus combines security-relevant signals, risk-based approvals, reports and URL reputation in a dedicated security perspective without making security depend on an administrator for every answer.
Approvals
Access Review Desk
See escalated requests with risk, reason, type and approval status directly in the security workflow.
Effect context
Change Effect Preview
Review criteria, reach and expected effect before the responsible role makes a decision.
History
Configuration Rollback
Place supported changes on a timeline and keep the prepared return path visible.
In the security workflow
Relevant risks become visible before decisions stall.
Security needs direct access to prioritized signals, approved reports and transparent cases, not broad console rights.
Assess signals directly
Use the security view to review status, source and the detail behind each signal.
See escalations in the dashboard
Review risk, reason and approval state without waiting for a forwarded screenshot.
Access approved reporting views
Use standard security, user-risk and audit extracts for the responsible assessment.
Combine sources transparently
Review ZIA and tenant-configured sources with response state, confidence and hard threat indicators.
From signal to decision
Security works with prioritized context.
Posture, risk assessment and approval remain connected in one understandable workflow.
Identify the signal
See which risks, trends or open cases need attention.
Assess the context
Use source status, user and policy context and the expected change effect.
Decide and retain evidence
Apply the tenant policy and keep reason, status, target effect and read-back together.
Nexus MetaScore
Use transparent source provenance instead of an isolated URL score.
Nexus MetaScore combines ZIA with external sources only when they are reviewed, licensed and connected for the tenant. It exposes response status, confidence and hard threat indicators.
- ZIA is the core source.
- Missing source responses remain visible.
- Tenant controls determine which external data paths are permitted.
Security operations
Reporting, risk and approval use the same context.
Security gains direct visibility while technical administration retains its own responsibility.
For security decision makers
Independent visibility improves decision quality.
Security can assess posture, URL risk, reports and open approvals without using the administrator as an information relay.
Next step
Review a security workflow
Bring one recurring operating situation. We will map the roles, required context and appropriate demo path.
Frequently asked questions
Zscaler security operations explained.
What does the Security Cockpit show?
It combines security-relevant tenant signals with source status and drill-down context in a role-specific view.
Which reports can security teams use?
The platform provides approved standard reporting views and extracts for security, user risk, approval activity and relevant audit context. Concrete content depends on tenant configuration.
How does Nexus MetaScore work?
It combines ZIA with tenant-configured and evidenced sources and shows which sources responded, their status, confidence and hard threat indicators.
How are security approvals controlled?
The tenant policy determines which authorized role decides and whether a separate second decision is required for the concrete workflow.
Further reading