What's Happening?
Drata has launched a private beta for its new Split Ticket Routing feature, designed to streamline compliance and remediation workflows for organizations using AWS and Jira. This new functionality allows Drata to create separate Jira tickets for failing
resources based on AWS account IDs or resource tags. Instead of a single, comprehensive ticket for all findings, each relevant team receives a ticket specifically detailing the failing resources they own. This aims to reduce the burden on a single point of contact for triage and provides teams with a scoped list of issues to address immediately. Key capabilities include creating routes to split tickets, assigning specific Jira owners and projects per account or resource, and attaching scoped CSV files containing only the relevant failing resources for each ticket. The feature is currently limited to AWS connections and Jira integrations.
Why It's Important?
This development is significant for U.S. businesses, particularly those operating large-scale cloud infrastructures on AWS and relying on Jira for project management and issue tracking. By enabling granular ticket routing, Drata addresses a common pain point in compliance and security operations: the inefficient distribution of remediation tasks. This can lead to faster resolution times for security vulnerabilities and compliance gaps, as teams are directly notified of issues pertinent to their specific AWS accounts or resources. The ability to assign tickets to specific Jira users and projects based on ownership within AWS can enhance accountability and operational efficiency. This feature is particularly beneficial for enterprises with complex organizational structures and numerous AWS sub-accounts, as it helps prevent a single team or individual from being overwhelmed by a consolidated list of findings, thereby improving overall security posture and compliance adherence.
What's Next?
Currently in private beta, Drata plans to announce the general availability of Split Ticket Routing in the future. Organizations interested in leveraging this feature will need active AWS, AWS Organizational Units (OU), or AWS GovCloud connections within Drata, along with a connected Jira integration that has write access. Users will need to configure mappings on their AWS connection's 'Ticket routing' tab, specifying AWS account IDs or resource tags, along with the corresponding Jira project and assignee. Once configured, Drata will automatically split tickets on the next scheduled sync. Future developments may include support for other cloud providers and ticketing tools beyond AWS and Jira, expanding the utility of this feature to a broader range of enterprise environments.
Beyond the Headlines
The introduction of Split Ticket Routing by Drata highlights a broader trend in the cybersecurity and compliance industry towards more intelligent, automated, and distributed remediation processes. As cloud environments become increasingly complex and distributed, the traditional model of centralized security operations often struggles to keep pace. This feature reflects an understanding that effective compliance and security require a decentralized approach, empowering individual teams with the specific information and tasks they need. This shift can foster a stronger 'security-as-code' culture, where security and compliance responsibilities are integrated directly into development and operations workflows. It also underscores the growing importance of seamless integration between compliance automation platforms and existing IT service management tools like Jira, moving towards a more cohesive and less siloed approach to governance, risk, and compliance (GRC).













