- User Portal
- About the Platform
- Getting Started
- About Tenants
- About Environments
- About PAAs and PIP Settings
- Identity Workspace
- Authorization Workspace
- Orchestration Workspace
- About Policies
- About the Certification Process
- About Audit Reports
- About the Policy Simulator
- Developer Portal
- Admin Portal
- Architecture Diagram and High-Level Components
- Key Platform Components
- Tenant Admin
- Policy Information Point (PIP)
- Policy Authorization Agent (PAA)
- Installing and Deploying PAAs
- PIP Operator Service
- Runtime Service Configuration
- Secret Management Configuration
- Managing Policy Authorization Agents
- Authorization Audit Configuration
- Working with the PlainID Docker Hub
- Kubernetes Deployment
- Standalone Deployment
- PAA Health Monitoring
- PAA Troubleshooting
- Caching Options
- Authorizers
- SaaS Authorization Management
- Token Enrichment Authorization Pattern
- API Access Authorization Pattern
- Data Access Authorization Pattern
- Access File Authorizer
- Amazon API Gateway
- Apigee
- Auth0
- Denodo
- Envoy
- Google BigQuery
- Istio
- Java Data Access SDK
- JSON Filtering Authorizer
- Microsoft Entra ID
- Microsoft Power BI
- NodeJS SDK
- Okta
- PlainID Token Enrichment Service
- Ping
- Snowflake
- SQL Database Authorizer
- Trino
- Zscaler Private Access (ZPA)
- 03 Jun 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
About Assets and Asset Types
- Updated on 03 Jun 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Asset Types
Asset Types are defined as logical groups of Assets that the Organization wishes to manage together. Asset Types are defined by a combination of Asset Attributes, Actions, and/or Rulesets. Applications are associated to Asset Types which means that Assets that match the Asset Type criteria can be consumed by the Applications associated to them.
The Policies you create in the Policy Catalog define which Organizations can have access to your business applications and what they can do Actions (such as order, view, edit, update, delete, etc.). And, the Applications are the method by which they can perform these Actions.
Some examples of Asset Types might be: a collection of databases or servers, a type of account (for example, loans or mortgage accounts), or a collection of resource files (for example, the total of a company's marketing assets - brochures, product catalogs, proposal templates, etc.).
When creating a new Policy, one of the steps you need to complete is to select the Asset Type for that Policy. Once you create an Asset Type, you can then associate Assets to it. Assets are defined by the Asset Type in which they were created.
Assets
Assets are defined as organizational resources for which the Organization creates Policies to control access. Typically, they are digital/electronic. A few examples of Assets are data files, specific servers or databases. Assets can be added to the Organization Management manually or by importing a .csv file. By default, an Asset is given a Name and Asset ID as mandatory Attributes. The Organization can add additional mandatory or optional Attributes as needed.
In most cases, the Organization will want to allow or deny a Member the ability to perform Actions on an Asset. Actions might include: view, update, approve, delete, etc. An Application in the Organization Management maps to a business application on the Organization or Customer side. For more information, see Managing Assets.