01 · Ownership

The right owner, suggested with a reason

One screen puts an owner on every required control in a programme. Cylanto suggests who, says why in words, and takes every top suggestion at once if you agree.

  • Drop in your organisation chart, and people, units and named roles are filled in for you.
  • One owner per control, requirement, check or policy. Anything unnamed falls to the owner above it, so nothing is left to nobody.
  • It tells you when the load sits with one person, and publishes a RACI and an access review as evidence.

Why it matters

Accountability you can read off the screen, instead of a spreadsheet of names that goes stale.

Takes every suggestion in one click
Ownership
Who owns SOC 2

12 of 31 required controls have an owner of their own. Dana Alcott answers for 61% of the requirements: spread it.

Assign all suggested
ControlWhat it isOwnerSuggested
CTL-IAM-04Multi-factor authentication is enforced for production and regulated-data accessRORita Okonkwo—
CTL-IAM-01Access is provisioned through an approved request and authorisation processDana Alcott, from the programmeRita Okonkwo
covers Access Control
CTL-CRY-02Data in transit is protected with strong cryptographyDana Alcott, from the programmeNoor Haddad
covers Network Security, Cryptography

02 · Policies

Policy acceptance that proves itself

Publish a policy and ask everyone to accept it. Each person gets a private link and needs no account. Cylanto keeps the list, chases the outstanding and writes the record.

  • See who has accepted, who has not, and how they did it.
  • The acknowledgement report is generated from the record, never uploaded.
  • Each policy moves from draft through approval to in force, with its next review on the calendar.

Why it matters

No more chasing signatures by email, and the proof an auditor wants already exists.

Information Security Policyapproved v3
Acceptance 46/52
PersonStatusHow
Luca Marchettiacceptedsigned in
Noor Haddadacceptedprivate link
Amara Bellooutstandinglink sent
Remind the outstandingAsk everyone to accept

03 · Requests

Evidence collected from whoever holds it

Every evidence request carries an owner, a due date and the period it must cover. Each person sees their own list, and someone with no login can still answer by a single-use link.

  • My work puts what is asked of you, what you still owe and the biggest next move in one place.
  • A request closes itself when the document arrives. Whoever supplied a document cannot also accept it.
  • Digest emails carry titles and links only, at most every fifteen minutes. The detail stays in the platform.

Why it matters

The work reaches the person who holds the answer, and the compliance team stops being the postbox.

14 No login

See what your stack already says about you.

Start with a discovery of your own domain. We will walk you through what we found, the frameworks that apply, who would own what, and where your evidence already stands.