Smart Vault for JSM

Stop pasting passwords in plain text. Smart Vault uses Rovo AI and AES-256 encryption to securely collect credentials directly within Jira Service Management.

Comment

🏎️ Inspiration: Speed vs. Security

In Formula 1, the Williams Racing Pit Crew performs miracles in seconds. But in IT Support, "Speed" often conflicts with "Security".

Service Management Agents are the "Pit Crew" of the enterprise. They are under immense pressure to resolve tickets fast. However, when customers paste raw passwords, API Keys, or Credit Card numbers into ticket comments, the workflow crashes. Agents have to stop, manually scrub data, and worry about compliance (GDPR/SOC2).

We asked ourselves: Can we bring F1 Pit Stop speed to Data Compliance?

🛡️ What it does

Smart Vault for JSM is an AI-powered secure enclave that allows Support Teams to handle sensitive data without compromising speed or security.

  • ⚡ Speed (The Rovo Copilot): Instead of manual data entry, Agents simply command Rovo AI: "Secure the credentials in this comment." Rovo instantly detects, categorizes, and encrypts the data.
  • 🎯 Precision (The Vault): Sensitive data is removed from plain text and stored in a secure, encrypted vault attached to the issue.
  • 🔒 Security (The Access Control): Data is encrypted using AES-256-GCM. Only authorized agents (with EDIT_ISSUES permission) can "Reveal" the data. Every access is logged in the ticket's internal audit trail.
  • 🛑 Prevention (Customer Portal): A dedicated "Secure Upload" button on the portal allows customers to send secrets safely from the start.

⚙️ How we built it

We prioritized a "Clean Room" architecture to ensure maximum security and performance:

  1. Native Forge UI Kit: We used UI Kit to ensure the app feels native, loads instantly, and respects Atlassian's design system.
  2. Rovo Agent: We tuned the System Prompt to act as a DLP (Data Loss Prevention) Expert, capable of distinguishing between Financial Data, PII, and IT Credentials.
  3. Cryptography: We implemented Node.js native crypto module with AES-256-GCM algorithm. Each entry uses a unique Initialization Vector (IV).
  4. Audit System: We post immutable internal comments whenever data is accessed or destroyed.

🔧 Challenges we ran into

  • The "Browser Sandbox" Constraint: Implementing a "Copy to Clipboard" button inside the Forge iframe sandbox was tricky due to browser permission policies. We had to implement a fallback mechanism (using Frame) to ensure a smooth UX.
  • AI Safety: Getting Rovo to acknowledge the encryption without repeating the secret password back in the chat was a critical safety hurdle. We used strict "Negative Constraints" in the prompt to prevent data leakage.

🏆 Accomplishments that we're proud of

  • Zero-Friction UX: The UI looks and feels exactly like a native Jira feature.
  • Enterprise Compliance: The automated Audit Log feature makes this tool ready for real-world enterprise use cases immediately.
  • Rovo "Turing Test": Our Agent can successfully parse complex sentences like "Here is the AWS key, and oh, use this IP address" and only encrypt the key.

🚀 What's next for Smart Vault

  • Auto-Redaction: Allowing Rovo to automatically edit the original comment to replace the password with [REDACTED].
  • Integrations: Connecting the backend to HashiCorp Vault or AWS Secrets Manager for enterprise clients.

Built With

Share this project:

Updates

Submission history