Skip to content

Trust center// Leasify App[+]

Security you can verify.

Leasify App is built for municipalities and corporate groups that answer to NIS2. Our security programme follows the directive's ten security measures, and this is where we show how far each one has come.

Leasify App // trust console

Awaiting data

Uptime // 30 d

—

NIS2 measures

1in place

10 in progress · 1 planned

  • 21.2 a Risk analysis and security policy: In progress
  • 21.2 b Incident handling: In place
  • 21.2 c Business continuity: In progress
  • 21.2 d Supply chain security: In progress
  • 21.2 e Secure development and vulnerability handling: In progress
  • 21.2 f Assessing effectiveness: In progress
  • 21.2 g Cyber hygiene and training: Planned
  • 21.2 h Cryptography and encryption: In progress
  • 21.2 i Access control and asset management: In progress
  • 21.2 j Multi-factor authentication: In progress
  • Art. 20 Management accountability: In progress
  • Art. 23 Incident reporting: In progress

Latest release // —

Hosting // EU

Programme// Directive (EU) 2022/2555

The ten NIS2 measures are our framework

Our customers must assess the security of their suppliers. Instead of a certificate on its own, we show every measure, what is in place and what we are working on, so you can assess us on facts.

Read the full programme

In place

1

of 12 areas

In progress

10

of 12 areas

Planned

1

of 12 areas

  1. 21.2 a

    Risk analysis and security policy

    NextSecurity policy being approved by management.

    In progress

  2. 21.2 b

    Incident handling

    NextAlerts to each affected customer, with an alert log, being added.

    In place

  3. 21.2 c

    Business continuity

    NextRecovery objectives and documented restore tests being introduced.

    In progress

  4. 21.2 d

    Supply chain security

    NextSecurity review of every subprocessor and a complete public subprocessor list under way.

    In progress

  5. 21.2 e

    Secure development and vulnerability handling

    NextVulnerability register and in-house penetration tests being introduced.

    In progress

  6. 21.2 f

    Assessing effectiveness

    NextControls being mapped to each NIS2 requirement.

    In progress

  7. 21.2 g

    Cyber hygiene and training

    NextTraining register per person, with renewal dates, to be introduced.

    Planned

  8. 21.2 h

    Cryptography and encryption

    NextCryptography policy being documented.

    In progress

  9. 21.2 i

    Access control and asset management

    NextAsset inventory and recurring access reviews being introduced.

    In progress

  10. 21.2 j

    Multi-factor authentication

    NextPer-customer passkey and YubiKey requirements being rolled out.

    In progress

  11. Art. 20

    Management accountability

    NextManagement approval of each measure and management training being documented.

    In progress

  12. Art. 23

    Incident reporting

    NextReport content, export and alerts to affected customers being built.

    In progress

Art. 23// incident reporting

Built around your 24 hours

For significant incidents we record when we became aware and track the deadlines for early warning, notification and final report, the same timeline you report against.

In progressReport content, export and alerts to affected customers.

  1. 0 h

    Aware

    The clock starts when we become aware of the incident.

  2. 24 h

    Early warning

    Whether it may be malicious and whether it can affect other countries.

  3. 72 h

    Notification

    A first assessment of severity and impact.

  4. 1 month

    Final report

    Root cause, threat type and what was done.

Verify// public records

Inside Trust// for Leasify and auditors

The ISMS behind this page

Leasify Trust is where we run the programme: requirements, controls, risks, incidents and evidence. Auditors and customers can apply for access.

  • Requirements

    NIS2 and customer questionnaires as sources, each requirement assessed.

  • Controls and risks

    Risk register with treatment plans and linked controls.

  • Incidents

    Lifecycle, actions, evidence and the NIS2 reporting timeline.

  • Documents

    Versioned policies with an approval flow.

  • Compliance calendar

    Recurring activities with evidence and deadlines.

  • Vault

    Secrets under AWS KMS envelope encryption, every access logged.