Multi Tenancy

Secure60 provides a robust multi-tenant architecture that supports complex organisational structures, from simple single-organisation deployments to sophisticated enterprise hierarchies with multiple subsidiary organisations. This flexible approach enables organisations to maintain data separation, implement granular access controls, and support diverse business requirements within a unified platform.


Organisational Hierarchy

Overview

Secure60’s organisational structure is built around a hierarchical model that mirrors real-world business relationships. Organisations can have multiple levels of sub-organisations, enabling enterprises to structure their security operations to match their business organisation.

Organisation Layers

The platform supports unlimited levels of organisational depth:

Key Characteristics


Organisational Structure Benefits

Business Alignment

Operational Efficiency

Compliance & Governance


Projects: Data Containers Within Organisations

Project Overview

Within each organisation, data is organised into Projects. Projects serve as logical containers for security data, allowing organisations to segment data based on business requirements, compliance needs, or operational considerations.

Project Characteristics

Common Project Patterns

Geographic Projects

Organisation: Global Corp
├── Project: North America
├── Project: Europe  
├── Project: Asia Pacific
└── Project: Latin America

Business Unit Projects

Organisation: Enterprise Inc
├── Project: Finance Department
├── Project: IT Operations
├── Project: Manufacturing
└── Project: Sales & Marketing

Environment Projects

Organisation: Tech Company
├── Project: Production Environment
├── Project: Staging Environment
├── Project: Development Environment
└── Project: Partner Integrations

Compliance Projects

Organisation: Financial Services
├── Project: PCI DSS Scope
├── Project: SOX Compliance
├── Project: General Operations
└── Project: Customer Data

Data Retention Control

Projects control data retention periods, allowing organisations to implement different retention policies based on business needs, compliance requirements, or cost considerations:

Retention Examples

Project: PCI DSS Compliance Data → 3 years retention
Project: General Security Logs → 1 year retention  
Project: Critical Infrastructure → 7 years retention
Project: Development Environment → 90 days retention

Project Management


User Management at Organisation Level

User Assignment Model

Users in Secure60 are assigned at the Organisation level, not at the project level. This design provides flexibility while maintaining administrative simplicity.

How User Access Works

Organisation Assignment

  1. Primary Organisation - Each user is assigned to a primary organisation
  2. Organisation Hierarchy - Users can access their assigned organisation and any sub-organisations
  3. Cross-Organisation Access - Users can be granted access to multiple organisations when needed
  4. Administrative Scope - Administrative privileges apply within the user’s assigned organisational scope

Project Access Control

Once assigned to an organisation, users can be granted specific permissions to projects within that organisation:

User Role Examples

Organisation Administrator

User: Jane Smith
Organisation: Global Corp (Root)
Access: All sub-organisations and all projects
Permissions: Full administrative access

Regional Security Manager

User: John Doe  
Organisation: Global Corp - Europe
Access: Europe organisation and sub-organisations
Permissions: Manage European projects and users

SOC Analyst

User: Alice Johnson
Organisation: Global Corp - North America
Project Access: Production Environment, Staging Environment
Permissions: Read access to security events, create investigations

Compliance Officer

User: Bob Wilson
Organisation: Global Corp (Root)
Project Access: PCI DSS Scope, SOX Compliance (across all regions)
Permissions: Read access to compliance-related data and reports

Inheritance and Configuration

Feature Inheritance Overview

Secure60’s multi-tenant architecture supports comprehensive feature inheritance between organisations, enabling parent organisations to share capabilities, configurations, and resources with their child organisations. This inheritance model promotes consistency, reduces administrative overhead, and ensures standardised security practices across the enterprise.

Inheritable Features

The following features can be inherited from parent to child organizations:

Feature Inheritance Flow

The diagram below illustrates how features flow from parent organisations to child organisations, enabling comprehensive inheritance of security capabilities:

Feature Inheritance Flow

As shown in the inheritance model:

Configuration Inheritance

Sub-organisations can inherit various configuration elements from their parent organisations:

Inheritable Elements

Customisation Options

Feature Inheritance Examples

Rule Inheritance

Parent Organisation: Global Security Baseline
├── Rule Group: Failed Authentication Detection
├── Rule Group: Malware Detection
└── Rule Group: Data Exfiltration Detection

Child Organisation: European Division
├── Inherits: All parent rule groups
├── Adds: GDPR-specific data access rules
└── Customises: Adjusted thresholds for regional patterns

Response Inheritance

Parent Organisation: Standard Incident Response
├── Email Notifications → Security Team
├── Ticket Creation → ITSM System
└── Automated Blocking → Firewall

Child Organisation: Finance Division
├── Inherits: All parent responses
├── Adds: Regulatory notification → Compliance Team
└── Enhances: Priority escalation for financial systems

Report Inheritance

Parent Organisation: Executive Reporting Suite
├── Monthly Security Dashboard
├── Compliance Summary Report
└── Threat Intelligence Briefing

Child Organisations: All Subsidiaries
├── Inherit: All parent reports with organisation-specific data
├── Customise: Branding and contact information
└── Extend: Additional local compliance reports

Data Retention Control

Parent Policy: Standard 7-year retention
├── Financial Sub-Org: 10 years (regulatory requirement)
├── Development Sub-Org: 1 year (cost optimization) 
├── PCI Environment: 3 years (PCI DSS compliance)
└── General Operations: 7 years (inherited policy)

Multi-Tenant Security

Feature Inheritance Benefits

The comprehensive feature inheritance model provides significant operational and security advantages:

Operational Efficiency

Flexibility and Control

Data Isolation

Administrative Separation


Implementation Best Practices

Planning Your Organisational Structure

  1. Map Business Structure - Align security organisation with business organisation
  2. Consider Compliance - Factor in regulatory requirements for different business units
  3. Plan for Growth - Design structure to accommodate future organisational changes
  4. Define Data Flows - Understand how data should flow between organisations

User Management Strategy

  1. Principle of Least Privilege - Grant minimum necessary access to each user
  2. Regular Access Reviews - Periodically review user access across organisations
  3. Role Standardisation - Develop standard roles that can be applied across organisations
  4. Onboarding/Offboarding - Establish clear processes for user lifecycle management

Feature Inheritance Strategy

  1. Inheritance Planning - Design which features should be inherited vs. customised at each organisational level
  2. Version Management - Establish processes for updating inherited features across the organisation
  3. Override Governance - Define clear policies for when child organisations can override inherited features
  4. Change Communication - Implement communication processes for feature updates that affect multiple organisations

Project Organisation

  1. Logical Grouping - Group related data sources into coherent projects
  2. Clear Boundaries - Ensure project boundaries align with business and compliance needs
  3. Retention Planning - Design project retention policies to balance compliance, cost, and operational needs
  4. Consistent Naming - Use consistent naming conventions across organisations
  5. Documentation - Maintain clear documentation of project purposes, scope, and retention requirements

Getting Started with Multi-Tenancy

Initial Setup

  1. Design Organisation Structure - Plan your organisational hierarchy
  2. Create Organisations - Set up parent and child organisations
  3. Configure Inheritance - Set up appropriate inheritance relationships
  4. Create Projects - Establish initial projects within organisations
  5. Assign Users - Add users to appropriate organisations with correct permissions

Migration Considerations

For detailed implementation guidance and step-by-step setup instructions, visit our Guides section.

Back to top