Borneo Data Stores v2.0 - Migration from ECS to Kubernetes and new Compliance De-scoping Assistance Workflow
Co-authored by: Sushim Mukul Dutta and Jan Hecking
The 2.0 release of Borneo for AWS Data Store is a great milestone that marks the move from Amazon’s Elastic Container Service (ECS) to Kubernetes (using Amazon Elastic Kubernetes Service, or EKS). This will allow Borneo’s Data Store platform to scale better and ease the mechanism of deployment, using Borneo CLI. This release also paves the path forward for supporting multi-region and multi-cloud deployments.
The new features in this release are focused on helping Compliance Engineers with their job of finding and fixing data compliance-related issues, with ease.
New Solutions and Features
Discover PII, financial information, and credentials in image files for stronger compliance posture
We’ve added image inspection capabilities to our inspection service component, to look into all popular image file formats and identify if they contain PII, credentials, or code secrets. The feature is particularly helpful for Fintech organizations’ data and security teams, to identify S3 buckets which are used by third-party vendors for doing KYC of their users. The support is extended to both continuous scanning and deep scanning on S3.
Perform deep scans on selected files for S3 for quicker discovery and remediation
We heard you! Data Security engineers can now directly trigger deep scans for selected files, instead of just defining the S3 bucket scan configuration and get the insights in minutes. This is particularly useful if you would want to know what PII resides within a particular file, without the hassle of scanning the entire S3 bucket. Watch it in action here:
Achieve PCI DSS compliance faster using the new Compliance De-scoping Assistance Workflow
The new compliance resource descoping workflow enables compliance engineers to achieve fast and automated compliance.
The workflow can be set up easily, and once turned on, will help identify any resources that could potentially impact compliance. It will also monitor these resources so that a continuous compliance check can be conducted. At the end, a data mapping report will be generated, which will include a record of the processing activity and incident resolution audit trail for all sources within the scope of compliance.
The workflow includes orchestration for PCI DSS. Other compliance standards can be added on request:
Discover India-specific PII and sensitive information
2.0 release’s major focus was to help compliance engineers discover data that impacts compliance posture in any form. In our first country-focused data discovery effort, compliance engineers can now look up Indian government IDs such as AADHAR card ID, PAN card ID, Indian Voter ID, and Indian Driver’s License along with Indian continent-specific PII such as Indian Bank Account Number, UPI Payment ID.
You can enable them from the Infotype configuration page as shown below:
Reduce incident noise for email address detection using Corporate Email Address infotype
Borneo is now able to differentiate between your employees’ corporate email addresses and your users’ email addresses. Though superficially the same, the presence of these two infotypes in your data can have very different implications from a compliance standpoint, and being able to differentiate between the two helps focus your compliance efforts.
Enhancements
Monitor daily Incident resolution status right on Incident’s Dashboard
We’ve added the Total Resolved and Total Unresolved Metrics cards to the Incident Dashboard to help with regular audits of how many incidents are being resolved.
If you have any questions, feel free to email us at sales@borneo.io. Want to see more of this and other Borneo’s solutions in action? Request a demo here with us, and we will get back to you soonest.