Needs-based access control

Trustle uses a unique blend of pragmatic and programmatic approaches to secure cloud systems. To support audit and regulatory requirements, Trustle provides approval workflows. For ongoing access activities, Trustle uses a combination approval status, risk score, and policy to determine the appropriate action. Of course, all of this activity is available as a history for certification and audit.

Traditional provisioning products rely on approval & re-certification workflows, which often create more work with little security benefit. Trustle automatically identifies and removes access from cloud systems when not in use, and restores them through simple requests.

Authorization engines require connected applications to support their proprietary APIs to talk to it. Trustle integrates natively with each cloud system to continuously configure appropriate access for each user account.

Trustle’s policy-based + self-service model makes getting access simple for authorized users. Here are the steps:

• System owners build a catalog of resources, specifying the sensitivity of the resource
• Team members can request access to resources
• Depending on policy, a manager or system owner may need to approve the request and (optionally) change the default duration for access
• The team member instantly gains access
• Trustle removes access after it expires, but the team member can regain access upon request

Trustle also offers on-call features, so response teams can act with immediacy. Any team member on an on-call list (such as in PagerDuty) can immediately access any system and resource that is approved for that purpose.