Bearer can generate two types of reports about your codebase, all from the same underlying scan.
7
+
Bearer can generate various types of reports about your codebase, all from the same underlying scan.
8
8
9
9
## Security Report
10
10
skipped 109 lines
120
120
121
121
The custom map file should follow the format used by [subject_mapping.json]({{meta.sourcePath}}/blob/main/pkg/classification/db/subject_mapping.json). Replace a key’s value with the higher-level subject you’d like to associate it with. Some examples might include Customer, Employee, Client, Patient, etc. Bearer will use your replacement file instead of the default, so make sure to include any and all subjects you want reported.
122
122
123
+
## Data Flow Report
124
+
125
+
The data flow report breaks down the data types and associated components detected in your code. It highlights areas in your code that process personal and sensitive data and where this data may be exposed to third parties and databases.
126
+
127
+
You can use this to gain more detailed insights beyond what the Privacy report offers, and build additional documentation like data catalogs. In the following example, we can see all the places an `Email Address` is processed by our [example application](https://github.com/Bearer/bear-publishing):
To run your first data flow report, run `curio scan` with the `--report dataflow` flag. By default, the data flow report is output in JSON format. To format as YAML, use the `--format yaml` flag.
Mark Michon
committed
1 year ago
1 parent c9c59c59