Exposure scanning
Inspect service projects for organization and participant sharing without reading request content.
Privacy Guard for Jira Service Management
Find unintended sharing before it becomes an incident.
A focused control plane for JSM Organizations and Request participants, with monitor-first policies and revalidated remediation.
- ✓Runs entirely on Atlassian
- ✓No remote backend or analytics
- ✓No request bodies or attachments
01 / THE PROBLEM
A single field can widen a sensitive audience.
HR, legal and security requests can inherit organization-wide visibility or unexpected participants. Claervo makes those sharing paths visible and controllable.
02 / THE CONTROL PLANE
Explainable risk
Prioritize findings using audience size, request context and deterministic policy signals.
Scoped policy
Target projects and request types, define allowed domains and begin in monitor-only mode.
Safe remediation
Clear prohibited organizations or remove only violating participants after current-state revalidation.
Private account mapping
Attribute a customer account for reporting without granting organization access.
Sanitized evidence
Keep a tenant-local audit trail and export CSV or JSON without unnecessary customer content.
03 / THE METHOD
Detect. Decide. Revalidate. Record.
Detect
Scan only the JSM metadata needed to understand sharing exposure.
Decide
Evaluate the request against explicit, scoped policies.
Revalidate
Fetch current Jira state again before any approved write.
Record
Preserve sanitized evidence for operations and audit.
04 / THE PRODUCT
Policy and protection in the same workflow.
C
05 / THE BOUNDARY
Customer metadata stays inside Atlassian.
Compute, Custom UI assets and application storage run in Atlassian Forge. There is no Claervo-operated remote processor, external database, advertising technology or product analytics endpoint.
Review securityPrivacy Guard for Jira Service Management