Skip to content

defenseunicorns/lula

Folders and files

NameName
Last commit message
Last commit date
Jan 31, 2025
Feb 5, 2025
Dec 10, 2024
Dec 17, 2024
Dec 20, 2024
Feb 13, 2025
Oct 22, 2024
Feb 5, 2025
Oct 3, 2023
May 31, 2024
Dec 10, 2024
Oct 7, 2024
Jan 31, 2025
Jan 31, 2025
Sep 19, 2024
Dec 11, 2023
Jan 28, 2025
Aug 29, 2022
Dec 13, 2024
Dec 12, 2024
Jan 28, 2025
Apr 1, 2024
Aug 23, 2024
Jan 17, 2025
Jan 17, 2025
Aug 30, 2024
Oct 23, 2022
Oct 25, 2023
Aug 2, 2024
Aug 16, 2024

Lula - The Cloud-Native Compliance Engine

Lula Documentation Go version OpenSSF Scorecard

lula logo

Lula is a tool designed to bridge the gap between expected configuration required for compliance and actual configuration.

Key Features

  • Assess compliance of a system against user-defined controls
  • Evaluate an evolving system for compliance over time
  • Generate machine-readible OSCAL artifacts
  • Accelerate the compliance and accreditation process

Why Lula is different than a standard policy engine

  • Lula is not meant to compete with policy engines - rather augment the auditing and alerting process
  • Often admission control processes have a difficult time establishing big picture global context control satisfaction, Lula fills this gap
  • Lula is meant to allow modularity and inheritance of controls based upon the components of the system you build

Overview

Cloud-Native Infrastructure, Platforms, and Applications can establish OSCAL documents that are maintained alongside source-of-truth code bases. These documents provide an inheritance model to prove when a control that the technology can satisfy IS satisfied in a live-environment.

These controls can be well established and regulated standards such as NIST 800-53. They can also be best practices, Enterprise Standards, or simply team development standards that need to be continuously monitored and validated.

Lula operates on a framework of proof by adding custom overlays mapped to the these controls, Lula Validations, to measure system compliance. These Validations are constructed by establishing the collection of measurements about a system, given by the specified Domain, and the evaluation of adherence, performed by the Provider.

Providers and Domains

Domain is the identifier for where and which data to collect as "evidence". Below are the active and planned domains:

Domain Current Roadmap
Kubernetes -
API -
File -
Cloud Infrastructure

Provider is the "engine" performing the validation using policy and the data collected. Below are the active providers:

Provider Current Roadmap
OPA -
Kyverno -

Getting Started

Install Lula and check out the Simple Demo to get familiar with Lula's validate and evaluate workflow to assess system compliance and establish thresholds. See the other tutorials for more advanced Lula use cases and information on how to develop your own Lula Validations!

Communication

For more information on how to get involved in the community, mailing lists and meetings, please refer to our community page

For security issues or code of conduct concerns, an e-mail should be sent to lula@defenseunicorns.com.