Application Onboarding Overview

1. Properly identified and categorized – Ensures each application is distinctively managed within the organization.
2. Linked to its operational environments – Ensures seamless integration and correct resource allocation across all stages.
3. Governed by security policies – Guarantees compliance with internal and regulatory security requirements before activation.

​

Key Steps

1. Provide Application Details
   Start by collecting essential metadata such as the application name, business category, the responsible team or owner, and a description of its purpose. This step ensures that every application is consistently tracked and properly classified for compliance.
2. Configure Environments
   Link the application to its deployment environments: Development, Staging, and Production. Connecting each environment to a Policy Store sets the foundation for enforcing access controls at each stage of deployment.
3. Configure Policy Store
   Define the authorization schema for the application by specifying three key elements: Principals (who is requesting access), Actions (which operations are allowed), and Resources (the data or items that need protection). Enrich policies with both static (user role) and runtime (access time) attributes, ensuring flexible policy enforcement.
4. Define the authorization schema with three core elements:

   Element	Examples	Purpose
   Principals	Users, systems	Who requests access
   Actions	Create, read, update	Operations allowed
   Resources	Patient records, documents	Protected data/items

5. Enrich the schema with additional attributes:
   • Static attributes (e.g., user role, department)
   • Runtime attributes (e.g., access time, location)
6. Configuration options:
   • Visual editor
   • Import templates/files
7. Test & Activate
   • Upload test data to simulate real-world scenarios, validating the policy behavior before activation. This ensures that policies function as expected in real-world conditions, preventing any surprises after the post-activation.
8. Go Live
   • Once validated and activated, the application is fully onboarded and ready for operational workflows, ensuring smooth transitions from testing to real-world usage.