Xoxoday: Least Privilege and Audit Admin Actions

​

Role-Based Access and Least Privilege

Xoxoday’s access control framework is anchored on the principle of least privilege. Access is role-based and provisioned only when operationally required — no user or service account holds more permissions than their role demands. This applies uniformly across all environments, from production systems to supporting infrastructure. Privileged access to Xoxoday’s IT infrastructure is restricted exclusively to the DevOps, Site Reliability Engineering (SRE), and engineering leadership teams. This narrow access scope limits the impact of any potential misuse or compromise — a foundational control required by ISO 27001 and SOC 2 Type II.

​

Tamper-Resistant Audit Trails

Every administrator action within Xoxoday is captured in comprehensive audit logs. These logs are stored in a separate, dedicated AWS account — isolated from the primary production environment — ensuring that no privileged user can modify or delete records of their own actions. Audit logs are reviewed on a monthly basis by authorised personnel, providing a consistent oversight cadence that supports compliance audits and internal governance reviews. For organisations connecting Xoxoday to their HR tech stack — whether via Workday, SAP SuccessFactors, or Darwinbox — this audit isolation means cross-system access events remain independently verifiable, even in the event of a security incident.

​

Time Synchronisation Across Infrastructure

Xoxoday’s entire IT infrastructure is synchronised using NTP (Network Time Protocol). Consistent timestamps across all systems are essential for correlating security events, reconstructing incident timelines, and meeting evidentiary requirements during compliance audits. Without reliable time synchronisation, log correlation across distributed services becomes ambiguous and legally unreliable.

​

Periodic Access Reviews and Segregation of Duties

User access and privileges across Xoxoday are reviewed periodically to ensure only current, necessary access is retained. Accounts that no longer require elevated permissions are downscoped or deprovisioned promptly, preventing privilege accumulation over time. Developer and maintenance roles are segregated at both the network and profile levels. This separation of duties prevents any single individual from holding unchecked control over critical systems — a control required by both SOC 2 Type II and ISO 27001. A developer working on application code, for example, cannot simultaneously access the network configuration layer governing production routing. This layered approach to access governance ensures Xoxoday maintains a strong security posture while enabling operational teams to work efficiently within clearly defined, auditable boundaries. Learn more: Xoxoday Help Centre — Security