Sample policy
Interpreting the sample policy
Here we show the same sample policy presented at the beginning of this
document. This policy manages the data locations EMAIL
, CCN
, and
SSN
, which map to email, credit card number, and social security
number data located in repositories claims
and loans
as defined in
the Data Map.
Based on the rules specified in this policy,
Users belonging to the user group
analyst
are allowed to read up to 10 rows at a time from any of the data locations covered by this policy, update 1 row at a time ofEMAIL
orCCN
data, and delete 1 row at a time from any of the data locations covered by this policy.As an exception, the user
bob
can read any amount of rows for any of the covered data locations, update any number of rows inEMAIL
orCCN
, and delete any number of records from any of the locations covered by this policy, but he can do this only when connected from a machine with the address192.0.2.22
or with an address in the range of the subnet203.0.113.16/28
.All other users (those who are not
bob
nor belonging to the groupanalysts
) can read 1 row ofEMAIL
at a time. Any other access to the data locationsEMAIL
,CCN
, andSSN
is disallowed.
data:
- EMAIL
- CCN
- SSN
rules:
- identities:
groups: [analyst]
reads:
- data: any
rows: 10
updates:
- data: [EMAIL, CCN]
rows: 1
severity: medium
deletes:
- data: any
rows: 1
severity: medium
- identities:
users: [bob]
hosts: [192.0.2.22, 203.0.113.16/28]
reads:
- data: any
rows: any
updates:
- data: [EMAIL, CCN]
rows: any
deletes:
- data: any
rows: any
- reads:
- data: [EMAIL]
rows: 1
To learn more, see the sample policy use cases.