- Platform Release 6.5
- Privacera Platform Release 6.5
- Enhancements and updates in Privacera Access Management 6.5 release
- Enhancements and updates in Privacera Discovery 6.5 release
- Enhancements and updates in Privacera Encryption 6.5 release
- Deprecation of older version of PolicySync
- Upgrade Prerequisites
- Supported versions of third-party systems
- Documentation changelog
- Known Issues 6.5
- Platform - Supported Versions of Third-Party Systems
- Platform Support Policy and End-of-Support Dates
- Privacera Platform Release 6.5
- Privacera Platform Installation
- About Privacera Manager (PM)
- Install overview
- Prerequisites
- Installation
- Default services configuration
- Component services configurations
- Access Management
- Data Server
- UserSync
- Privacera Plugin
- Databricks
- Spark standalone
- Spark on EKS
- Portal SSO with PingFederate
- Trino Open Source
- Dremio
- AWS EMR
- AWS EMR with Native Apache Ranger
- GCP Dataproc
- Starburst Enterprise
- Privacera services (Data Assets)
- Audit Fluentd
- Grafana
- Ranger Tagsync
- Discovery
- Encryption & Masking
- Privacera Encryption Gateway (PEG) and Cryptography with Ranger KMS
- AWS S3 bucket encryption
- Ranger KMS
- AuthZ / AuthN
- Security
- Access Management
- Reference - Custom Properties
- Validation
- Additional Privacera Manager configurations
- Upgrade Privacera Manager
- Troubleshooting
- How to validate installation
- Possible Errors and Solutions in Privacera Manager
- Unable to Connect to Docker
- Terminate Installation
- 6.5 Platform Installation fails with invalid apiVersion
- Ansible Kubernetes Module does not load
- Unable to connect to Kubernetes Cluster
- Common Errors/Warnings in YAML Config Files
- Delete old unused Privacera Docker images
- Unable to debug error for an Ansible task
- Unable to upgrade from 4.x to 5.x or 6.x due to Zookeeper snapshot issue
- Storage issue in Privacera UserSync & PolicySync
- Permission Denied Errors in PM Docker Installation
- Unable to initialize the Discovery Kubernetes pod
- Portal service
- Grafana service
- Audit server
- Audit Fluentd
- Privacera Plugin
- How-to
- Appendix
- AWS topics
- AWS CLI
- AWS IAM
- Configure S3 for real-time scanning
- Install Docker and Docker compose (AWS-Linux-RHEL)
- AWS S3 MinIO quick setup
- Cross account IAM role for Databricks
- Integrate Privacera services in separate VPC
- Securely access S3 buckets ssing IAM roles
- Multiple AWS account support in Dataserver using Databricks
- Multiple AWS S3 IAM role support in Dataserver
- Azure topics
- GCP topics
- Kubernetes
- Microsoft SQL topics
- Snowflake configuration for PolicySync
- Create Azure resources
- Databricks
- Spark Plug-in
- Azure key vault
- Add custom properties
- Migrate Ranger KMS master key
- IAM policy for AWS controller
- Customize topic and table names
- Configure SSL for Privacera
- Configure Real-time scan across projects in GCP
- Upload custom SSL certificates
- Deployment size
- Service-level system properties
- PrestoSQL standalone installation
- AWS topics
- Privacera Platform User Guide
- Introduction to Privacera Platform
- Settings
- Data inventory
- Token generator
- System configuration
- Diagnostics
- Notifications
- How-to
- Privacera Discovery User Guide
- What is Discovery?
- Discovery Dashboard
- Scan Techniques
- Processing order of scan techniques
- Add and scan resources in a data source
- Start or cancel a scan
- Tags
- Dictionaries
- Patterns
- Scan status
- Data zone movement
- Models
- Disallowed Tags policy
- Rules
- Types of rules
- Example rules and classifications
- Create a structured rule
- Create an unstructured rule
- Create a rule mapping
- Export rules and mappings
- Import rules and mappings
- Post-processing in real-time and offline scans
- Enable post-processing
- Example of post-processing rules on tags
- List of structured rules
- Supported scan file formats
- Data Source Scanning
- Data Inventory
- TagSync using Apache Ranger
- Compliance Workflow
- Data zones and workflow policies
- Workflow Policies
- Alerts Dashboard
- Data Zone Dashboard
- Data zone movement
- Workflow policy use case example
- Discovery Health Check
- Reports
- How-to
- Privacera Encryption Guide
- Overview of Privacera Encryption
- Install Privacera Encryption
- Encryption Key Management
- Schemes
- Encryption with PEG REST API
- Privacera Encryption REST API
- PEG API endpoint
- PEG REST API encryption endpoints
- PEG REST API authentication methods on Privacera Platform
- Common PEG REST API fields
- Construct the datalist for the /protect endpoint
- Deconstruct the response from the /unprotect endpoint
- Example data transformation with the /unprotect endpoint and presentation scheme
- Example PEG API endpoints
- /authenticate
- /protect with encryption scheme
- /protect with masking scheme
- /protect with both encryption and masking schemes
- /unprotect without presentation scheme
- /unprotect with presentation scheme
- /unprotect with masking scheme
- REST API response partial success on bulk operations
- Audit details for PEG REST API accesses
- Make encryption API calls on behalf of another user
- Troubleshoot REST API Issues on Privacera Platform
- Privacera Encryption REST API
- Encryption with Databricks, Hive, Streamsets, Trino
- Databricks UDFs for encryption and masking on PrivaceraPlatform
- Hive UDFs for encryption on Privacera Platform
- StreamSets Data Collector (SDC) and Privacera Encryption on Privacera Platform
- Trino UDFs for encryption and masking on Privacera Platform
- Privacera Access Management User Guide
- Privacera Access Management
- How Polices are evaluated
- Resource policies
- Policies overview
- Creating Resource Based Policies
- Configure Policy with Attribute-Based Access Control
- Configuring Policy with Conditional Masking
- Tag Policies
- Entitlement
- Service Explorer
- Users, groups, and roles
- Permissions
- Reports
- Audit
- Security Zone
- Access Control using APIs
- AWS User Guide
- Overview of Privacera on AWS
- Configure policies for AWS services
- Using Athena with data access server
- Using DynamoDB with data access server
- Databricks access manager policy
- Accessing Kinesis with data access server
- Accessing Firehose with Data Access Server
- EMR user guide
- AWS S3 bucket encryption
- Getting started with Minio
- Plugins
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- Privacera Platform documentation changelog
Models
Models detect specific data elements in your data resources. The detection is done with various algorithms and heuristics.
Types of models
Privacera supports different types of models. You can filter the list of models using the search model option. This tab also displays the present number of record count.
Generic models
These are various general model parameters you can use to tailor matching of data.
Parameter | Data Type | Default | Description |
---|---|---|---|
| String | None | Patterns to be matched. Can contain more than one pattern by changing the value of the |
| String | None | Patterns to be excluded from matching. Can contain more than one pattern by changing the value of the |
| Boolean | FALSE | Indicates whether matching should use only the digits. Setting this parameter TRUE removes all non-numeric characters in the string before matching. For example, |
| String | None | Indicates whether to evaluate a checksum digit based on the last digit. Valid values:
|
| Boolean | FALSE | Indicates whether to use patterns specified by the |
| String | None | A dictionary name or key. See Dictionaries. |
| String | None | Pattern for matching. See Patterns. NoteSee Embed Patterns in Dictionaries. |
| Boolean | FALSE | Indicates whether to use Privacera-defined matching to validate an ISO two-character country code. If this parameter is set to TRUE, |
| None | A valid pattern for matching country codes. See Patterns. NoteSee Embed Patterns in Dictionaries. | |
| None | Name of a defined dictionary. See Dictionaries. |
Credit card model
The credit card model detects credit card numbers. It validates numbers based on the issuing network, length, and Luhn checksum.
Parameter | Type | Default | Meaning |
---|---|---|---|
| String | Privacera-supplied pattern for credit card numbers with range of digits, space or hyphen separated. | Credit card pattern, if you want to override the supplied pattern. |
| Boolean | True | Validate against known issuing network prefixes. |
| Boolean | True | Validate the Luhn checksum on the credit card number. |
Supported credit card types
Credit Card Type | Conditions | Examples |
---|---|---|
American Express (AMEX) Card | Credit card starting with 34 or 37 and having 15 digits. | 34xxxxxxxxxxxxx 37xxxxxxxxxxxxx |
Master Card |
| 51xxxxxxxxxxxx 2221xxxxxxxx 27xxxxxxxxxxx |
Visa Card | Credit card starting with 4 and having 13 Or 16 digits. | 4xxxxxxxxxxxx 4xxxxxxxxxxxxxxx |
Diners Club Card | Credit card starting with 300 to 305 or 3095 or 36 or 38 or 39 and having 14 digits. | 300xxxxxxxxxxx 3095xxxxxxxxxx |
VPay (Visa) Card | Credit card starting with 4 and having 13 or 19 digits. | 4xxxxxxxxxxxx 4xxxxxxxxxxxxxxxxxx |
Date of birth model
The Date of Birth model detects various date formats.
Parameter | Type | Default | Meaning |
---|---|---|---|
| Integer | 5 | Age lower threshold. |
| Integer | 100 | Age upper threshold. |
| Boolean | True | Tagging is done based on an algorithm to detect random distribution. |
| String | – | Pattern that matches a custom date format var1. |
| String | – | Date Format that matches the pattern for var1. |
Pre-configured date formats are:
International YYYYMD format with 4 digit year
US MDY with 4 digit or 2 digit year
Month abbreviated MDY
Additional formats can be configured. For example, configure a regex and a Java date format:
Parameter | Type |
---|---|
|
|
|
|
EIN model
The EIN model detects Employer Identification Number using patterns and digit validation.
Parameter | Type | Default | Meaning |
---|---|---|---|
| String | Default | EIN digit pattern if you want to override the default pattern. |
| Boolean | True | Age upper threshold. |
| Boolean | True | Allow match only if EIN has exact format. |
Geo latitude and longitude model
The geo model detects latitude and longitude coordinates. It can validate these values based on a geographical area.
Parameter | Type | Default | Meaning |
---|---|---|---|
| Double | US min latitude | Lower limit (southern) on latitude. |
| Double | US max latitude | Upper limit (northern) on latitude. |
| Double | US min longitude | Lower limit (west) on longitude. |
| Double | US max longitude | Upper limit (east) on longitude. |
| Integer | 3 | Minimum number of digits after the decimal point. |
IMEI model
The IMEI model detects International Mobile Equipment Identity numbers that are used to identify mobile phones. It validates the Luhn checksum and the length of the IMEI.
ITIN model
The ITIN model detects Individual Tax Identifier Numbers (identifiers of individual taxpayers). It validates the format and digits of the ITIN.
Parameter | Type | Default | Meaning |
---|---|---|---|
| String | Default | ITIN digit pattern if you want to override the default pattern. |
| Boolean | True | Allow match only if ITIN has exact format. |
MIME model
The MIME model detects a file based on its Multipurpose Internet Mail Extensions type. The MIME type is detected using a combination of file extension and magic bytes in the header of the file. The detected MIME type is then looked up in a dictionary of MIME types.
Parameter | Type | Default | Meaning |
---|---|---|---|
| String | – | Identifier of dictionary of MIME types. |
There are two pre-configured MIME model instances.
For detecting executable files:
LOOKUP_DICT=EXEC_MIME_KEYWORD
.For detecting image files:
LOOKUP_DICT=IMAGE_MIME_KEYWORD
.
Phone number model
The Phone Number model detects phone numbers. It validates the format of the phone numbers based on the country for which it is configured.
Parameter | Type | Default | Meaning |
---|---|---|---|
| String | US | Two-character country code. |
SSN model
The SSN model detects US Social Security Numbers. It validates the format and checks against a blacklist of SSN numbers.
Parameter | Type | Default | Meaning |
---|---|---|---|
| String | Default | Override the default SSN pattern. |
| Boolean | True | Validate against known blacklist of SSNs. |
| Boolean | False | Allow match only if SSN has exact format. |
| Boolean | False | Match against any nine digit number without format. |
| Boolean | False | Match against any four digit number without format. Disables validation with blacklist of SSN. |
| Boolean | True | Allow match only if SSN has exact format that is hyphen-, dot-, or space-separated. |
Examples of Invalid SSNs
The SSN model would determine that the following SSNs are invalid.
SSN starting with 9 or 666 or 000 or 98765432.
SSN with 00 as the 4th and 5th digits.
SSN with 0000 as the sixth through ninth digits.
Any SSN like these:
123456789
111111111
222222222
333333333
444444444
555555555
666666666
777777777
888888888
999999999
VIN model
The VIN model detects Vehicle Identification Numbers. It validates the length and the VIN checksum.
Zip model
The Zip model detects US Zip codes. It detects both 5 digit and 5+4 digit variations and validates against a dictionary of US Zip codes.
Parameter | Type | Default | Meaning |
---|---|---|---|
| String |
| Key of the US Zip dictionary. |
| String | Default | Validates content regular expression for list of ZIP codes. |
| Boolean | False | Allow match only if Zip code has exact format. If set to true then only nine digits containing '-' and starting with five digits are considered a Zip code. |
Create a model
To create a model, follow these steps:
From the navigation menu, select Discovery > Models.
Click Add Model.
The Add Model dialog is displayed.
In the Name field, enter a name for the model.
In the Description field, enter a description of the model.
In the Key field, enter a model key.
From the Type dropdown menu, select a model type.
Note
See Types of Models for more information.
From the Apply For dropdown menu, select File content.
Note
File content is resource content.
Enable or disable the model using the Model Status toggle.
Add model properties by clicking +.
Enter a key and value into the Key and Value field. For example: Key: MIN_FRACTIONAL_DIGITS, Value: 2. You can add multiple model properties.
Note
For example: Key:
MIN_FRACTIONAL_DIGITS
, Value: 2. You can add multiple model properties.Click Save.
The model is created.
Edit a model
You can edit a model by clicking the Edit icon in the Actions column.
To edit a model, follow these steps:
Click the Edit icon in the Actions column.
The Edit Model dialog displays.
Make your desired changes.
Click Save.
The model is updated.
Delete a model
You can edit a model by clicking the Delete icon in the Actions column.
To delete a model, follow these steps:
Click the Delete icon in the Actions column.
The Confirm Delete dialog displays.
Select Delete to confirm the deletion.
The model is deleted.
Import a model
To import a model file in JSON format, follow these steps:
In the Models home page, click the Import option.
The Import dialog is displayed.
Browse and select the JSON file and click Import.
The model file is imported.
Export a model
To export a model file in JSON format, follow these steps:
In the Models page, click Export.
From the drop-down menu, select one of the following options:
All Records: Export the entire set of models.
Select Records: Select the specific model to export. You can select multiple models.
Click Export.
The JSON file is exported.
List of Privacera-supplied models
The following is a list of the Privacera-supplied models. For precise details, look at the model itself in the Platform UI.
DOB_ML_MODEL
CC_ML_MODEL
ZIP_ML_MODEL
IMEI_ML_MODEL
SSN_ML_MODEL
EXEC_ML_MODEL
MIME_ML_MODEL
PHONE_NUMBER_ML_MODEL
GEO_LAT_LONG_ML_MODEL
CC_ML_MODEL_PROTECTED
EIN_ML_MODEL
ITIN_ML_MODEL
VIN_ML_MODEL
SSN_9_DIGIT_ML_MODEL
SSN_4_DIGIT_ML_MODEL
IMAGE_FILE_ML_MODEL
IMAGE_ML_MODEL