Skip to main content

Platform Relationships

This page provides comprehensive visual representations of all primary relationships between compliance objects in the Openlane platform, making it easier to understand how different components interact and depend on each other.

Primary Relationships Table

Source ObjectRelated ObjectRelationship TypeDescription
ControlsStandardsImplementationControls implement specific requirements from compliance standards
ControlsEvidenceDemonstrationEvidence demonstrates that controls are properly implemented
ControlsRisksMitigationControls are implemented to mitigate specific risks
ControlsProgramsOrganizationControls are organized and managed within compliance programs
ControlsTasksExecutionTasks track the work required to implement and maintain controls
EvidenceControlsSupportEvidence demonstrates that controls are implemented effectively
EvidenceProgramsOrganizationEvidence collection is organized within compliance programs
EvidenceStandardsRequirementsEvidence requirements are defined by compliance standards
EvidenceTasksCollectionTasks are created to collect and maintain evidence
EvidenceFilesStorageEvidence often includes file attachments and documents
RisksControlsMitigationControls are implemented to mitigate specific risks
RisksAction PlansTreatmentAction plans define steps to address and mitigate risks
RisksProgramsManagementRisks are managed within compliance programs
RisksTasksAssessmentTasks are created to assess and monitor risks
RisksAssetsAssociationRisks are often associated with specific IT assets
GroupsOrganizationsStructureGroups belong to organizations and provide internal structure
GroupsUsersMembershipUsers are members of groups and inherit permissions
GroupsEntitiesAccess ControlGroups control access to specific business entities
GroupsControlsResponsibilityGroups are assigned responsibility for controls
GroupsEvidenceManagementGroups collect, review, and maintain evidence
OrganizationsUsersMembershipUsers are members of organizations
OrganizationsGroupsStructureGroups provide organizational structure within organizations
OrganizationsEntitiesOwnershipOrganizations own and manage business entities
OrganizationsProgramsManagementOrganizations manage compliance programs
OrganizationsControlsImplementationOrganizations implement and maintain controls
ProgramsOrganizationsOwnershipPrograms are owned and managed by organizations
ProgramsStandardsImplementationPrograms implement specific compliance standards
ProgramsControlsCoordinationPrograms organize and coordinate control implementation
ProgramsEvidenceCollectionPrograms coordinate evidence collection and organization
ProgramsTasksManagementPrograms manage tasks and activities for compliance
TasksUsersAssignmentTasks are assigned to users for completion
TasksProgramsOrganizationTasks are organized within compliance programs
TasksGroupsCoordinationGroups coordinate task assignments
TasksControlsImplementationTasks implement, validate, and maintain controls
TasksEvidenceCollectionTasks coordinate evidence collection and organization

Relationship Network Diagram

Detailed Relationship Categories

Organizational Structure

  • Organizations → Groups, Users, Entities, Programs
  • Groups → Users, Entities (access control)
  • Users → Tasks (assignment), Groups (membership)

Compliance Framework

  • Programs → Standards, Controls, Evidence, Tasks
  • Standards → Controls, Evidence (requirements)
  • Controls → Evidence, Risks, Tasks

Risk Management

  • Risks → Controls (mitigation), Tasks (assessment), Assets (association)
  • Controls → Risks (address), Evidence (demonstrate)

Evidence and Documentation

  • Evidence → Controls (support), Programs (organization), Files (storage)
  • Files → Evidence (contain), Programs (document)

Operational Execution

  • Tasks → Users (assigned to), Programs (organized by), Controls (implement)
  • Groups → Tasks (coordinate), Evidence (manage)

Common Relationship Patterns

1. Hierarchical Relationships

Organizations
├── Groups
│ └── Users
├── Entities
│ └── Assets
└── Programs
├── Controls
├── Evidence
└── Tasks

2. Cross-Functional Relationships

  • ControlsEvidenceTasks (Implementation cycle)
  • RisksControlsPrograms (Risk management cycle)
  • StandardsProgramsEvidence (Compliance cycle)

3. Access Control Relationships

  • OrganizationsGroupsUsers (Permission inheritance)
  • GroupsEntitiesAssets (Scope control)
  • UsersTasksEvidence (Responsibility chain)

Primary Functional Relationships

Organizational Relationships

Operational Relationships

Usage Tips

  1. Start with Organizations: Begin relationship mapping from the organization level
  2. Follow the Flow: Use the diagram to trace relationships between objects
  3. Understand Dependencies: Some relationships are dependent (e.g., Evidence depends on Controls)
  4. Plan Implementation: Use relationships to plan implementation order
  5. Troubleshoot Issues: Use relationships to identify potential integration points

This visual representation helps you understand how all compliance objects interconnect and supports better decision-making when designing compliance programs and workflows.