Bedrock Data routes data-exposure fixes to owners and checks results
Original title: Bedrock Data routes data exposure fixes to owners and verifies results
The feature is generally available with the platform and uses existing Jira or ServiceNow tickets.
Bedrock Data said its AI-assisted remediation identifies the owner of an exposed dataset, opens a ticket in the customer’s Jira or ServiceNow workflow, and explains the finding in context. When a ticket is closed, the platform checks whether the exposure is gone and reopens it if not. Security teams can write natural-language routing rules, and defined policies can revoke document sharing without a workflow. The company cites its own survey and EY and IBM reports on AI and breach costs.
Unconfirmed: Survey and breach-cost figures are cited from Bedrock, EY, and IBM reports, not independently verified here.
- Tickets are created, routed, and validated inside existing ITSM tools.
- Owners can ask questions such as who can access a file inside the ticket.
- A policy can revoke sharing by sensitivity and notify the owner.
- Bedrock says ticket records support PCI DSS 4.0.1, SOC 2, and NYDFS Part 500 reviews.
- Its index says 76% blamed lack of automation for holding back data security.
- Vendors
- Bedrock Data
- Products
- JiraServiceNow
- Organizations
- Sportradar
From the original article
4 min read at helpnetsecurity.comBedrock Data has announced AI-assisted remediation, which federates the work of fixing data exposure to the data owners across the enterprise. Bedrock Data discovers who owns each exposed dataset, opens a ticket for that owner in the Jira or ServiceNow workflow the enterprise already runs and supplies the context needed to fix it.
By Industry News · helpnetsecurity.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.