BigID API/Scan Data In Motion Tutorial: Difference between revisions
| Line 30: | Line 30: | ||
let tokenReq = await window.fetch('https://sandbox.mybigid.com/api/v1/sessions', { | let tokenReq = await window.fetch('https://sandbox.mybigid.com/api/v1/sessions', { | ||
method: 'POST', | method: 'POST', | ||
headers: [{'content-type':'application/json'}], | |||
body: JSON.stringify({username: "bigid", password: "learner"}) | body: JSON.stringify({username: "bigid", password: "learner"}) | ||
}); | }); | ||
Revision as of 04:06, 9 March 2022
- The differences between data in motion scans and regular data source scans
- How to test a connection to a data in motion data source
- How to add a data source using the BigID API
Many organizations are receiving and processing data in real time. Where there's data, there's bound to be personal information. In this tutorial, we'll add an AWS Kinesis data source that BigID will scan in real time.
Unlike traditional BigID scans that run weekly, monthly or quarterly, data in motion scans run continuously. This means that under scan details you'll see your data in motion scan at 0% with a status of "in progress" while you're monitoring a data in motion data source.
First, we should check if data in motion is enabled in your environment.
Discovering Data Sources
You can see what data source connectors are installed in your environment through the BigID UI, but since we're focused on the API (and because all actions in the UI can be performed in the API), we are going to use the API to retrieve them.
Press Send on the request below to get a listing of the data source connectors installed on our test BigID system.
You'll see our test system has around 70 different data source connectors installed. Use CTRL+F (CMD+F on Mac OS) to search for the Kinesis connector.