LISA FAQ

Answers before you evaluate LISA

Understand how LISA works, where it runs, how your compliance data is handled, and what licensing options are available.

Frequently asked questions

What prospective teams ask about LISA

What is LISA GRC?

LISA GRC is self-hosted governance, risk and compliance software designed to help organizations structure and manage NIS2 compliance work. It brings assessments, controls, evidence, remediation and management visibility together in one operational workspace.

Who is LISA designed for?

LISA is designed for organizations that need a structured way to manage NIS2 governance, controls, evidence, remediation and compliance visibility while retaining control of their deployment and data.

What parts of the compliance lifecycle does LISA support?

LISA connects the compliance lifecycle from assessment through management and evidence to reporting. Teams can evaluate requirements, manage controls and responsibilities, track remediation work and deadlines, maintain supporting evidence, and give leadership visibility into progress and gaps.

Does using LISA make my organization NIS2 compliant?

No. LISA is a compliance-support tool, not a legal determination, certification or guarantee of compliance. It helps organizations structure, assess and document compliance activities, but results and outputs must be independently reviewed and, where appropriate, verified by qualified legal or compliance professionals.

Which compliance frameworks does LISA support?

LISA currently focuses on structured NIS2 compliance operations, including assessments, controls, implementation progress, evidence and remediation. The compliance model is designed to support additional structured framework content without fragmenting governance and evidence processes.

Where is LISA deployed?

LISA is self-hosted and designed to run within infrastructure your organization controls, rather than depending on a shared hosted compliance environment. This gives your organization control over the deployment environment and operating model.

Who controls our compliance data and evidence?

With the self-hosted model, compliance records and supporting evidence remain within the environment your organization operates. Your organization controls the infrastructure, access and operational governance around that environment.

How does LISA handle compliance evidence?

LISA keeps supporting evidence connected to the compliance work it substantiates. Evidence can be maintained in context alongside assessments, controls and remediation work, helping teams preserve traceability instead of separating evidence from the work it supports.

How is LISA operated and maintained?

LISA is designed as an installable, self-hosted product. Its delivery is supported by deployment, configuration, operations and upgrade guidance so organizations can install and manage LISA within their own environment.

How is LISA licensed?

LISA is available through self-hosted licensing designed for organizations that want greater control over their compliance software environment. The self-hosted offering uses a perpetual software license rather than requiring a shared hosted service.

Is source-code licensing available?

Yes. A source licensing option is available for organizations that need internal maintenance or customization capability. This option provides the corresponding source release and can be discussed based on the organization and deployment requirements.

Can we see LISA before deciding?

Yes. You can request a private demo to see how LISA approaches NIS2 assessments, controls, evidence, remediation and management visibility, and to discuss your deployment and compliance requirements.

Still have a question?

See LISA in your own evaluation context.

Request a private demo to discuss your NIS2 workflow, deployment requirements and licensing options.