IllumiDesk Security Docs
  • IllumiDesk Team Handbook
  • People Group
    • Introduction
    • General Employment
    • Employment Status & Recordkeeping
    • Working Conditions & Hours
    • Employee Benefits
    • Employee Conduct
    • Timekeeping & Payroll
  • Security and Compliance
    • Security Controls
      • BC.1.01 - Business Continuity Plan
        • IllumiDesk Business Continuity Plan
        • IllumiDesk Disaster Recovery
        • IllumiDesk Reference Architectures
        • IllumiDesk Handbook listing of DR for Databases
      • BC.1.0.2 - Business Continuity Plan: Roles and Responsibilities
      • BC.1.03 - Continuity Testing
      • BC.1.04 - Business Impact Analysis
        • Business Impact Analysis in the handbook
        • Data Protection Impact Assessment (DPIA) Policy
        • Data Protection Impact Assessments or DPIAs
        • UX Department
        • Triage Operations - Communication about expected automation impact
        • NIST BCP with reference to BIA
      • CFG.1.01 - Baseline Configuration Standard
        • Laptop or Desktop System configuration
        • Configuring New Laptops
        • Security Best Practices
      • CFG.1.03 - Configuration Checks
        • Production Change Requests Policy
      • CM.1.01 - Change Management Workflow
      • CM.1.02 - Change Approval
      • CM.1.03 - Change Management Issue Tracker
      • CM.1.04 - Emergency Changes
      • DM.1.01 - Data Classification Criteria
        • Data Classification Policy
      • DM.2.01 - Terms of Service
        • Application Terms of Use
      • DM.4.01 - Encryption of Data in Transit
        • Deprecate support for TLS 1.0 and TLS 1.1
      • DM.7.03 - Data Retention and Disposal Policy
      • IAM.1.01 - Logical Access Provisioning
        • Access Requests
        • Access Management Process
      • IAM.1.02 - Logical Access De-Provisioning
        • Access Management Process
        • Logical Access Deprovisioning
        • Access Reviews
        • IllumiDesk Offboarding Guidelines
      • IAM.1.04 - Logical Access Review
        • Access Reviews
      • IAM.1.05 - Transfers: Access De-Provisioning
        • Access Control Policy and Procedures
        • Job Transfers
        • Access Change Request
      • IAM.1.06 - Shared Logical Accounts
        • Security Process and Procedures for Team Members
        • Access Management Process
      • IAM.1.08 - New Access Provisioning
        • Access Requests
        • Access Management Process
      • IAM.2.01 - Unique Identifiers
        • Unique Account Identifiers
        • Access Control Policy and Procedures
        • Section on shared accounts in Okta handbook page
        • Access Management Process
      • IAM.2.02 - Password Authentication
      • IAM.2.03 - Multi-factor Authentication
      • IAM.3.02 - Source Code Security
      • IAM.4.01 - Remote Connections
      • IAM.6.01 - Key Repository Access
      • IR.1.01 - Incident Response Plan
      • IR.1.03 - Incident response
      • IR.1.04 - Insurance Policy
      • IR.2.02 - Incident Reporting
      • NO.1.01 - Network Policy Enforcement Points
      • PR.1.01 - Background Checks
      • RM.1.01 - Risk Assessment
      • RM.1.02 - Continuous Monitoring
        • Security Compliance
      • RM.1.04 - Service Risk Rating Assignment
      • RM.1.05 - Risk Management Policy
      • RM.3.01 - Remediation Tracking
      • SDM.1.01 - System Documentation
      • SG.1.01 - Policy and Standard Review
      • SG.2.01 - Information Security Program Content
      • SG.5.03 - Security Roles and Responsibilities
        • Incident Management Roles and Responsibilities
      • SG.5.06 - Board of Director Bylaws
        • Governance Documents
      • SG.5.07 - Board of Directors Security Program Content
        • Audit Committee Agenda Planner
      • SLC.1.01 - Service Lifecycle Workflow
      • SLC.2.01 - Source Code Management
      • SYS.1.01 - Audit Logging
      • SYS.2.01 - Security Monitoring Alert Criteria
      • SYS.2.07 - System Security Monitoring
      • TPM.1.01 - Third Party Assurance Review
      • TPM.1.02 - Vendor Risk Management
      • TRN.1.01 - General Security Awareness Training
        • Security Awareness Training
      • TRN.1.02 - Code of Conduct Training
      • VUL.1.01 - Vulnerability Scans
      • VUL.1.03 - Approved Scanning Vendor
      • VUL.2.01 - Application & Infrastructure Penetration Testing
      • VUL.3.01 - Infrastructure Patch Management
      • VUL.3.02 - End of Life Software
      • VUL.4.01 - Enterprise Protection
      • VUL.5.01 - Code Security Check
      • VUL.6.01 - External Information Security Inquiries
  • VPAT Version 2.3
Powered by GitBook
On this page
  • IllumiDesk's Security Controls
  • 1. Security
  • 2. Availability
  • 3. Processing integrity
  • 4. Confidentiality
  • 5. Privacy
  • IllumiDesk Trust Control Framework (ITCF)
  1. Security and Compliance

Security Controls

An introduction to IllumiDesk security controls and how the SOC2 trust principles are used within the organization.

PreviousTimekeeping & PayrollNextBC.1.01 - Business Continuity Plan

Last updated 1 year ago

IllumiDesk's Security Controls

IllumiDesk bases its security controls on the . SOC2 defines trust service categories that service organizations should implement. Generally, the implementation of these trust principles begin with the definition of controls. Then, the controls reference policies and procedures that document how the controls are implemented within an organization. Finally, the organization should maintain verifiable evidence that the policies and procedures referenced by the organization's controls are being adequately followed.

The five trust principles are summarized below:

1. Security

The security principle refers to protection of system resources against unauthorized access. Items such as web application firewalls (WAF), two-factor authentication, and vulnerability scans are examples of tools that organizations use to ensure the proper security policies are in place.

2. Availability

The availability principle refers to the accessibility of information used by the entity’s systems as well as the products or services provided to its customers. Accessibility standards are usually established by the entity's service level agreements (SLAs). Business continuity plans and disaster recovery plans are examples of policies and procedures defined by the organization to meet availability controls.

3. Processing integrity

Processing integrity refers to the completeness, validity, accuracy, timeliness, and authorization of system processing (i.e., delivers the right data at the right price at the right time). Monitoring access to data and ensuring ETL pipelines are properly implemented are two examples of how entities can ensure processing integrity.

4. Confidentiality

Information designated as confidential is protected to meet the entity’s objectives. Organizations should have criteria defined to classify confidential information. Procedures to secure confidential data, such as encrypting data in transfer and at rest, are part of how an entity provides adequate procedures to protect confidential data from prying eyes.

5. Privacy

Personal information is collected, used, retained, disclosed, and disposed of to meet the entity’s objectives. Although confidentiality applies to various types of sensitive information, privacy applies only to personal information. An organization needs to consider applicable laws and regulations, as well as industry and client-specific privacy requirements when defining policies and procedures to protect private data.

IllumiDesk Trust Control Framework (ITCF)

IllumiDesk has tried to take a comprehensive approach to our immediate and future security compliance needs. Instead of attempting to juggle various requirements in parallels such as PCI, ISO, and SOC2, IllumiDesk has adopted standard SOC2 trust principles to establish a baseline trust control framework.

SOC for Service Organizations: Trust Services Criteria