Lightbeam Basics: Managing Sensitive Structured Data in Databases
Lightbeam discovers and protects PII in structured databases like MySQL, PostgreSQL & MongoDB—manage risks and ensure compliance.
Lightbeam Basics: Managing Sensitive Structured Data in Databases
Your structured databases may hold more risk than you realize.
In this Lightbeam Basics video, learn how to:
Locate PII across MySQL, PostgreSQL, MongoDB, and other databases
Identify whose sensitive data you hold and assess associated risks
Take action with policy-driven protection to ensure compliance and privacy
Lightbeam gives you complete visibility into structured data, helping you safeguard sensitive information and simplify compliance.
Transcript
Today we're gonna take a look at structured sensitive data
in the Lightbeam platform.
From the dashboard, we can see a widget
that shows us the information about
structured sensitive data.
We can see the number of databases and tables
and if there's any alerts or actions needed.
We wanna take a deeper dive. Let's look at the screen.
So here we see a list of the data sources
that are structured tables.
So we have MySQL, mssql, and Postgres.
You see, we have two instances of MySQL.
So each data source, if it's an in individual instance,
is separated From this screen.
We can see the name, the source, the owner, any alerts
that have been raised, the current status,
and if there's custom labels, atti assigned
to each of these data sets.
You can take one more step down and look in Postgres.
We can see a hard screen for Postgres here.
We can see the number of tables, the number of databases,
the amount of attributes, and uh, more interesting stuff.
So look here is we see 100 under attributes,
social security numbers.
So the in its entirety,
social security numbers are called out here.
Let's take a deeper dive and look at these tables.
The table screen, we can see a list
of all the tables in the Postgres environment.
It includes the name schema database that it belongs to,
the columns with PII.
So here we see specific tables
and what data sets are included of columns, number of rows,
columns with PII.
So employee table, obviously we would have a lot there.
In addition to the tables, we can also see the relationship
between the tables and the clusters.
These examples of a parent table,
orphan table, or a customer table.
New sets or new views of data can be created
by clustering data together,
like beam has no problem scanning these, uh, in relation
in each of the tables.
These are the identities of people who were found.
These are the entities from the entity level,
we can see number of attributes
that are scared if it's a human entity or a device,
and whether there's a risk been identified.
So we wanna go one more level
and look at Hannah's information.
We can see the specific information
that Postgres in these tables is holding for Hannah.
This makes fulfillment
of individual rights, automated process.
That's a look at databases in Lightbeam.
in the Lightbeam platform.
From the dashboard, we can see a widget
that shows us the information about
structured sensitive data.
We can see the number of databases and tables
and if there's any alerts or actions needed.
We wanna take a deeper dive. Let's look at the screen.
So here we see a list of the data sources
that are structured tables.
So we have MySQL, mssql, and Postgres.
You see, we have two instances of MySQL.
So each data source, if it's an in individual instance,
is separated From this screen.
We can see the name, the source, the owner, any alerts
that have been raised, the current status,
and if there's custom labels, atti assigned
to each of these data sets.
You can take one more step down and look in Postgres.
We can see a hard screen for Postgres here.
We can see the number of tables, the number of databases,
the amount of attributes, and uh, more interesting stuff.
So look here is we see 100 under attributes,
social security numbers.
So the in its entirety,
social security numbers are called out here.
Let's take a deeper dive and look at these tables.
The table screen, we can see a list
of all the tables in the Postgres environment.
It includes the name schema database that it belongs to,
the columns with PII.
So here we see specific tables
and what data sets are included of columns, number of rows,
columns with PII.
So employee table, obviously we would have a lot there.
In addition to the tables, we can also see the relationship
between the tables and the clusters.
These examples of a parent table,
orphan table, or a customer table.
New sets or new views of data can be created
by clustering data together,
like beam has no problem scanning these, uh, in relation
in each of the tables.
These are the identities of people who were found.
These are the entities from the entity level,
we can see number of attributes
that are scared if it's a human entity or a device,
and whether there's a risk been identified.
So we wanna go one more level
and look at Hannah's information.
We can see the specific information
that Postgres in these tables is holding for Hannah.
This makes fulfillment
of individual rights, automated process.
That's a look at databases in Lightbeam.
