Bearer's Dashboard is updated with a new Project view as its Home. This change is intended to help users find the correct information more efficiently by putting all the details about a given Project under one roof.
A Project is either a codebase from Git(Hub/Lab) or an AWS Datastore. For Large organizations, we hope this will help users to get a clearer and less overwhelming navigation to the correct information.
We have released our Jira Integration!
To ease collaboration, you can now create Jira Tickets from Risk Events cards or link them to an existing Jira Ticket.
Jira statuses are automatically retrieved and displayed in linked cards.
Check our documentation for more details and deployment instructions.
Our integration page went through a major improvement. We are preparing it to receive many more interconnection capabilities in source code and production.
Now find all the integrations Bearer supports and will support in the feature at one place.
We have improved Bearer API's Token feature. You can now create multiple token and revoke them when needed.
This brings additional security to Bearer deployments and improved maintainability.
Bearer now detects security risks that cause data breaches by scanning your code repositories.
Customer benefits are:
Risk events are listed on the Home page in an inbox format.
A risk event is triggered when:
Bearer provides you with contextual information so you can investigate and assess risks efficiently. Once a risk has been detected, you can ignore it, assign it to a teammate or close it once it has been mitigated.
Risk events can be customized in the Settings to fit your own processes. For each risk event you can set up:
For more information, please refer to the documentation.
Every Monday morning, users receive a report by email. This report summarizes the previous week's detections.
Users can proactively investigate new detections to identify and assess associated security risks that may lead to a data breach.
The Bearer Broker used to discover and classify data by scanning OpenAPI, SQL, GraphQL, and Protobuf files only.
Data discovery and classification capabilities have been extended to the entire codebase in the following languages:
The general mechanics is that it looks for Objects (e.g., User) and their properties or attributes (e.g., lastname).
You just need update the broker by running docker pull bearersh/broker:latest
For more information please refer to the documentation.
The Integrations and Interfaces tabs on the Component page have been merged for better readability.
On the page of a Component - let's call it Repository A - you can now see:
Months of iterations and dozens of user feedback led us to improve our User Interface.
Data discovery and classification are now fully automated.
Bearer’s detection engine supports 120+ data types, including personal, health, and financial data. See the full list of data types here.
You can create your own data categories - which regroup data types - to fit your data taxonomy.
Data type processed can be seen in your inventory and on the page of a component.
