Security, Governance and Platform Operations
What this domain tests
Security, governance, and platform operations covers who can do what in LifeTime and Service Center, how end users authenticate, how actions are audited, and how to operate the platform without creating privilege or compliance gaps.
Core rules
- IT Roles control platform administration and deployment rights; Teams grant access to applications and modules. Keep production deployment rights limited and separate from development rights.
- End-user authentication is configured per environment, for example built-in, Active Directory, or SAML, while end-user roles authorize application features. Do not confuse end-user roles with IT roles.
- Use a dedicated service account for CI/CD with only the IT role needed to deploy; never store its password in a module or pipeline log.
- Audit logs in LifeTime record administrative and deployment actions. Review them for who deployed which tagged version, when, and to which environment.
- Platform operations include patching Platform Server, managing certificates and SSL, backing up the platform database, and monitoring capacity. In OutSystems Cloud, some operations are provider-managed; self-managed installations keep them in-house.
- Use governance checks such as architecture and security dashboards before promotion, and require approval for Production.
Worked example
An auditor asks who deployed Orders 2025.06.1 to Production. You open LifeTime audit logs, filter by environment and deployment, and find the CI/CD service account performed the deployment at 02:10, matching the pipeline run. The approval record shows the release manager approved it. If the log instead showed a developer's personal account, you would remove that Production role and move the deployment to the service-account pipeline.
Traps
Granting Administrator in Production to developers; sharing accounts; assuming SSL is enabled without checking; treating end-user roles as IT roles; ignoring audit logs until an incident; and storing secrets in application configuration instead of a secure parameter store.