
OSCAL tools help you read, validate, write, convert and exchange machine-readable compliance information. Some are browser utilities. Others are developer libraries, assessment integrations or full compliance platforms.
Use the task selector below to find a starting point, then compare the tools and their documented limits. You will also find the directories, repositories and content registries where new OSCAL projects appear.
Last reviewed: 19 October 2026. This directory covers the entries in NIST's OSCAL Tools directory, OSCAL.io's Tools directory and the Tools section of Awesome OSCAL reviewed on this date, plus selected additional projects with public documentation. Older and unavailable entries are identified below. Secani builds some of the tools included here; descriptions are based on published documentation, not a benchmark of every implementation. For the underlying concepts, start with What is OSCAL?.
| What do you want to do? | Start here | What to check |
|---|---|---|
| Open an OSCAL file and understand its contents | Easy Dynamics OSCAL Viewer | The viewer accepts OSCAL JSON; check support for your document model. |
| Check an OSCAL JSON document without installing software | Secani OSCAL Validator | The public tool currently checks the OSCAL 1.2.2 JSON Schema layer. |
| Validate in CI, convert XML/JSON/YAML or resolve a profile | NIST OSCAL CLI or OSCAL CLI Enhanced | These are different distributions. Pin the distribution and supported OSCAL release. |
| Author compliance documents through Git reviews | Trestle and Agile Authoring | Decide how contributors will edit Markdown, structured data and approvals. |
| Add OSCAL to your own application | Libraries and CLIs | Match the programming language, models, serialization and validation depth. |
| Produce SSPs, assessment packages or POA&Ms | Commercial platforms | Verify the exact imported and exported models, not just an OSCAL badge. |
| Work with BSI IT-Grundschutz | BSI tools | Distinguish official framework content from third-party conversions and AI enrichment. |
| Find catalogs, profiles or examples | Content registries and examples | Check the publisher, framework revision, OSCAL version and content license. |
These sites serve different purposes. A tool directory helps you discover software; a content registry provides the documents that software can process.
| Website | What you can find | Useful starting point |
|---|---|---|
| NIST OSCAL Tools | NIST's own libraries and utilities, with active and archived entries identified. | Java CLI, liboscal-java and OSCAL-XSLT. |
| NIST project structure | How the OSCAL repositories and their supporting toolchains fit together. | Find the correct upstream repository and dependencies. |
| OSCAL.io Tools | Community listings with source, license, access and international filters. | Viewers, authoring tools, SDKs, BSI projects and Telos Xacta. |
| Awesome OSCAL | A broad community index of tools, content, articles and demonstrations. | Smaller utilities and older projects; follow through to each current repository. |
| GitHub's OSCAL topic | Repositories tagged by their maintainers. | Discover recent experiments and inspect releases, licenses and issues. |
| OSCAL Compass projects | The Trestle and Compliance-to-Policy family, SDKs and related projects. | Compare Git-based authoring and policy integration. |
| OSCAL Compass repositories | Source code for the Compass tools, including newer agent integrations. | Current READMEs, release notes and examples. |
| Metaschema Framework | Independent Java tooling, OSCAL CLI Enhanced and supporting libraries. | Check this distribution separately from the NIST repositories. |
| NIST OSCAL workshops | Tool demonstrations, implementation discussions, slides and recordings. | Discover implementations before community directories add them. |
| OSCAL.io documentation | Community guidance, registry APIs and OSCAL REST conventions. | Understand how tools exchange and retrieve documents. |
| OSCAL Foundation | Community initiatives, working groups and implementation resources. | Follow ecosystem work and reusable implementation patterns. |
NIST workshop presentations and community listings are discovery resources. They do not certify a product's conformance or endorse a vendor.
Use a viewer to inspect an existing document. Use an editor or authoring workflow when you need to change content, review it and preserve the result.
| Tool | What it helps with | Project and documentation |
|---|---|---|
| Easy Dynamics OSCAL Viewer | Browser-based navigation of JSON catalogs, profiles, component definitions, SSPs, assessment plans, assessment results and POA&Ms. Local-file processing stays in the browser; loading a URL requests that remote resource. | Open viewer · Source |
| RegScale OSCAL Hub | A workbench with a web UI, REST API and CLI for validation, conversion, profile resolution, batch processing and document management. It includes a backend and storage. This is separate from the OSCAL.io Content Registry. | Source and setup |
| Easy Dynamics OSCAL Editor Deployment | A Docker deployment combining a web frontend and REST service for viewing and editing local OSCAL JSON. Editing coverage varies by model and workflow; the older React dependency is archived. | Source · Local deployment |
| Compliance Trestle / Trestle SDK | Python SDK and CLI for creating and maintaining OSCAL through a compliance-as-code workflow. Supports JSON/YAML and Markdown authoring patterns; XML requires a separate conversion step. | Source and documentation |
| OSCAL Compass Agile Authoring | Setup and workflow templates for collaborative authoring, Git reviews, provenance and versioning using Trestle. A workflow toolkit rather than a hosted editor. | Source and setup |
| OSCAL Compass Agentic Agile Authoring | Agent-assisted authoring workflows and reusable instructions around the Compass toolchain. Generated implementation descriptions still need review. | Source |
| Trestle MCP | An MCP interface connecting assistants to Trestle operations. Check the exposed tool set for the workflow you want to automate. | Source |
| OSCALFlow | A TypeScript GitHub CLI extension for SSP skeletons, code-based implementation indicators, optional Copilot assistance and HTML reports. Indicators and generated text require assessment; they do not establish that a control is implemented. Optional AI features send code and control requirements to GitHub Copilot. | Source and commands |
| Control Freak | A Ruby on Rails application for searching and exploring NIST SP 800-53 controls. A focused catalog application rather than a universal OSCAL document editor. | Source |
| OSCAL Insights | A Compass visualization and demonstration project for exploring OSCAL data. Useful for implementation ideas; check its example scope. | Source |
Trestle was originally contributed by IBM and is now part of the OSCAL Compass CNCF project. Older articles and directories may still use the IBM name.
A library with OSCAL data types, a schema validator and a semantic validator solve different problems. The validation checklist below explains what to ask for.
| Tool | What it helps with | Project and documentation |
|---|---|---|
| Secani OSCAL Validator | Free browser-local checks of OSCAL 1.2.2 JSON, with readable errors. The public validator checks schema structure and documents its profile combine.method compatibility patch; it does not currently expose the toolkit's full semantic layer. | Open validator |
| Secani OSCAL Validation API | HTTP validation with a machine-readable report for CI and integrations. Unlike the browser tool, the API sends documents to Secani's servers for transient processing. Its current validation level is schema. | API documentation |
| NIST OSCAL Java CLI | Command-line validation, XML/JSON/YAML conversion and profile resolution. A standard starting point for Java-based OSCAL processing. | Source · NIST tools |
| OSCAL CLI Enhanced | An independent distribution with OSCAL validation, conversion, profile resolution and additional tooling. Verify the release and model support for the enhanced distribution you install. | Source · Documentation |
| liboscal-java | Java parsing, serialization and OSCAL processing. NIST and the independent Metaschema Framework publish separate distributions; select the matching dependencies. | NIST · Metaschema Framework |
| NIST OSCAL-XSLT | XSLT utilities for displaying and transforming OSCAL, primarily XML. This is the current home for XSLT work previously published in the archived OSCAL Tools collection. | Source |
| Metaschema Java and XSLT toolchains | Foundational tools for generating bindings, schemas and related model artifacts. These support OSCAL tooling rather than provide a complete compliance application. | NIST Java · Independent Java · NIST XSLT |
| go-oscal | Go types, schema validation, version revision and model-generation utilities. Schema checks do not imply complete semantic validation. | Source and documentation |
| OSCAL Compass oscal-sdk-go | An early Go SDK for OSCAL processing. Its README explicitly lists OSCAL constraint validation as unsupported. | Source |
| Roscal | Rust model library and CLI for inspecting documents, splitting them into editable workspaces, merging and validation. Check the implemented commands separately from the project's roadmap. | Source and CLI guide |
| OSCAL Pydantic / Pydantic v2 | Python models generated from OSCAL definitions, with Pydantic runtime type enforcement. Check the package variant and its supported model release. | Source · v2 package |
| pyOSCAL and pyOSCAL-Builder | Python object models, plus a generator that builds them from OSCAL Metaschema. | Library · Builder |
| OSCAL in Ruby | Ruby models for XML/JSON/YAML parsing and serialization. The current README documents OSCAL 1.2.1, including the mapping model; do not assume the next release is interchangeable. | Source |
| ValidateOscalDocuments | A C# library and console application for validating OSCAL XML against XML schemas. JSON/YAML processing is outside the documented current scope. | Source |
| GSA oscal-js | JavaScript/TypeScript helpers and an installer/wrapper around the Java OSCAL CLI. Requires Java; it is not a pure JavaScript validation engine. | Source |
| Easy Dynamics OSCAL REST | OSCAL API definitions and a partial Java reference service with file-based persistence. The API specification and the running service are distinct resources. | Specification · Service |
| OSCAL Club oscal-cli-action | Run an OSCAL CLI in GitHub Actions. An integration wrapper; callers supply requirements such as checkout and the Java runtime. | Source |
| asdf-oscal-cli | Install and switch Java OSCAL CLI versions with asdf. | Source |
| SHR Group OSCAL CLI container | Package the Java OSCAL CLI in a container. Check the selected upstream tag and image currency. | Source |
| Nix package for oscal-cli | A community Nix derivation for the Java CLI. The linked source pins a specific CLI package version; this is not the same thing as an OSCAL model version. | Package source |
| OSCAL Compass SDK Conformance | Development specifications and tests for SDK behavior. A resource for implementers, not a certification mark for products. | Source |
| Secani OSCAL toolkit and CLI | TypeScript processing, semantic validation and profile-resolution work described in our technical documentation. Currently in private preparation for an open-source release, rather than a publicly installable package. | Toolkit status · CLI status · Validation research |
These tools connect control descriptions, configuration policies, tests and assessment outputs. Some consume OSCAL; others export it from a different internal model.
| Tool | What it helps with | Project and documentation |
|---|---|---|
| Compliance-to-Policy (C2P) | Python tooling connecting compliance definitions to policy administration and assessment integrations, including Kyverno, Open Cluster Management and Auditree. | Source |
| Compliance-to-Policy Go | Go-based policy integration with pluggable providers. The repository distinguishes stable v1 from experimental v2/main. | Source |
| ComplyTime complyctl | Retrieve Gemara policies from OCI registries, run scanner providers and generate reports including OSCAL output. The current core uses Gemara. | Source · Quickstart |
| go-gemara / oscalexport | Convert Gemara control catalogs into OSCAL catalogs, and guidance catalogs into OSCAL catalogs or profiles. This is an export bridge between different models. | Source |
| RSpec OSCAL Formatter | Produce OSCAL assessment plans and assessment results from Ruby tests carrying the appropriate metadata. | Source and examples |
| MITRE inspec-oscal | A proof of concept for supplying InSpec inputs from OSCAL component information. | Source |
Looking for the original Lula compliance validator? It moved to Lula 1 and is in maintenance mode. The current Lula repository describes a different GitOps product. See the older-project notes below before following an old tutorial.
OSCAL also appears in German compliance tooling. The following are third-party projects; a BSI-related name does not make the tool or an enriched catalog an official BSI publication.
| Tool | What it helps with | Project and documentation |
|---|---|---|
| NTT DATA BSI Grundschutz Edition 2023 Converter | Convert module PDFs into an enriched OSCAL JSON catalog. The suite includes pruning, translation and component-related utilities. The main conversion workflow uses cloud AI. | Source · Directory listing |
| NTT DATA BSI Grundschutz Audit Automator | Cloud-based processing of audit documents into draft plans, checks, findings and reports for review. Source available under the Business Source License; this is not an open-source license. | Source · License |
| NTT DATA Grundschutz++ OSCAL Components Creator | OSCAL.io lists component generation and migration from Edition 2023 requirements. The linked primary repository could not be verified in this update. | Community listing |
| NTT DATA Grundschutz++ OSCAL Workbench | OSCAL.io describes catalog viewing, profile/SSP authoring, assessment and POA&M workflows. Treat this as a directory-listed project until you verify its current distribution and data processing. | Community listing |
For framework context, see Grundschutz++ and OSCAL. Before using an AI-assisted tool with audit evidence, check whether it sends documents to a hosted model or storage service.
The table describes documented OSCAL operations rather than ranking vendors. Availability can depend on the product module, deployment and subscription. SSP, SAP, SAR and POA&M are common package terms; in OSCAL, assessment plans and results use the assessment-plan and assessment-results models.
| Platform | Documented OSCAL use | Product or technical documentation |
|---|---|---|
| RegScale | OSCAL JSON imports and SSP exports; its documentation also describes FedRAMP SSP, SAP, SAR and POA&M exports in OSCAL XML. The commercial platform is separate from OSCAL Hub. | Export documentation · CLI libraries |
| Paramify | Import existing SSPs in Word or OSCAL and generate OSCAL SSP and POA&M documentation. | SSP import · POA&M documentation |
| Telos Xacta | OSCAL profiles and authorization packages, translated export validation and data exchange through the relevant Xacta modules. | OSCAL capabilities · Xacta Xchange |
| DRTConfidence | Author, validate, convert and exchange OSCAL SSP, SAP, SAR and POA&M packages. | Product · Document conversion |
| ServiceNow Continuous Authorization and Monitoring | OSCAL catalog and SSP imports and assessment-plan exchange in CAM. This is a capability of the CAM product and its supported release. | Import documentation · Assessment plans |
| Archer Assessment & Authorization | OSCAL import documented for the on-premises 2025.12 release. This evidence does not establish a full export capability. | Release notes |
| Vanta | OSCAL JSON export of controls, tests and evidence for eligible government frameworks, including a Trust Center resource regenerated on download. | FedRAMP documentation · Trust Center resource |
| Secureframe | OSCAL SSP generation and export in federal compliance workflows. POA&M management is described separately; do not infer OSCAL POA&M export from that alone. | FedRAMP product page |
| Ignyte Assurance Platform | OSCAL content consumption and content APIs for assessment and FedRAMP automation. Public material does not provide a complete model-by-model interchange matrix. | OSCAL capabilities |
| Ramper | FedRAMP continuous-monitoring workflows with POA&M export in OSCAL JSON and Excel. | OSCAL POA&M export |
| Rizkly | Control editing, existing-SSP intake and OSCAL SSP, SAP and SAR generation. Confirm the accepted import format. | OSCAL documentation |
| ASSYST ComplySyncATO | Machine-readable OSCAL evidence generation and API integration with compliance workflows. Exact supported models need confirmation. | Product |
| Knox Systems | A managed federal-cloud offering that documents OSCAL SSP and POA&M generation from application and infrastructure information. | OSCAL workflow |
| Second Front Game Warden | A managed DevSecOps offering whose vendor listing describes OSCAL-native controls and machine-readable compliance exports. The listing does not enumerate every exported model. | Vendor marketplace listing |
| Kovr at Fortreum | Compliance artifact generation and OSCAL exports from code, configuration, infrastructure and policy information. Confirm the required output model and format. | Product · OSCAL export statement |
| Secani | A shared compliance workspace connecting scopes, evidence, tasks and the agent. Evaluate the workspace for your authoring and review process; its public OSCAL validator and API are listed separately above. | OSCAL toolkit · Explore Secani |
There are also deployment and integration options: stackArmor's ThreatAlert integration with DRTConfidence connects environment information to OSCAL package generation. It uses DRTConfidence rather than establishing a separate general-purpose OSCAL engine.
Some products use OSCAL internally without documenting interchange. For example, Drata describes OSCAL-backed baseline parameter selection. That is useful context, but the cited feature alone does not establish OSCAL file import or export.
| Tool | What it helps with | Project and documentation |
|---|---|---|
| CivicActions compliance-io | OpenControl-to-OSCAL migration functions and JSON serialization for SSPs and component definitions. The README labels the library alpha and incomplete. | Source |
| CivicActions SSP Toolkit | Maintain SSP source material in an OpenControl/Markdown workflow; its compliance-io integration supports component-definition export. | Source and OSCAL notes |
| GoComply oscalkit | Go SDK and CLI for OSCAL format conversion, schema validation and related document operations. Check compatibility with the OSCAL release you need. | Source |
| GoComply FedRAMP utility | Convert OpenControl content to an OSCAL SSP and generate Word documents from OSCAL. DOCX conversion is documented as work in progress. | Source |
| Metanorma coradoc-oscal | An authoring example and converter from human-readable AsciiDoc/Coradoc controls to OSCAL YAML catalogs. | Source |
| oscal4neo4j | Cypher scripts for exploring OSCAL relationships in Neo4j. The repository uses CC BY-NC 4.0, which restricts commercial use. | Source and license |
| Red Hat OpenControl Database / ATO Pathways | A reference application for exploring OpenControl component content, with OSCAL JSON/XML and FedRAMP DOCX output paths. Current model/template compatibility needs checking. | Source |
| OSCAL Profile Import Examiner | A browser/XML demonstration for analyzing control selections against bundled NIST reference content. It does not fetch the actual imported targets and is not a general profile resolver. | Open demonstration |
| oscal-diagrams | Generate model relationship diagrams from Trestle/Pydantic models with Python and erdantic. Diagram coverage follows the installed model version. | Source |
Older tools remain useful when maintaining an existing pipeline or understanding a design. Check their status before starting a new deployment.
| Project | Status and useful context | Source |
|---|---|---|
| NIST OSCAL Deep Diff | Archived. JSON comparison CLI and library retained as historical tooling. | Repository |
| NIST OSCAL Tools | Archived. The maintained XSLT work moved to OSCAL-XSLT; the old collection also contains demonstrations. | Repository · Successor |
| OSCAL Content Authoring Tool / OSCAL-CAT | Archived early graphical catalog-authoring tool. | Repository |
| Easy Dynamics OSCAL React Library | Archived/read-only. Its README points ongoing development to the current OSCAL Viewer. | Old library · Current viewer |
| ComplyScribe / trestle-bot | Archived Trestle workflow automation. Consider the current complyctl workflow with its different Gemara-based core and OSCAL outputs. | Repository · complyctl |
| Red Hat oscal-automation-libs | Deprecated shared scripts and Makefiles. Its documented successor path leads to the older trestle-bot/ComplyScribe family. | Repository |
| Brian Ruf OSCAL-GUI | Archived pre-release prototype. Its README states it is incompatible with published OSCAL versions. | Repository |
| Lula 1 | The original OSCAL compliance validator. Its successor repository states maintenance mode, with no active feature development. | Original validator · Project transition |
| GovReady-Q | Questionnaire-based compliance application. Its published OSCAL integration notes reference older release-candidate component imports; establish compatibility before reuse. It is not labeled archived here. | Repository · OSCAL notes |
| Compliance Trestle FedRAMP plugin | Beta tooling around legacy FedRAMP validation content. Its results do not establish acceptance under current program requirements. | Repository |
| GSA OSCAL Generation Tool | A legacy ASP.NET prototype targeting pre-1.0 Milestone 3 schemas. | Repository |
| GSA OSCAL-to-Word examples | Separate SSP, SAP and SAR conversion examples. Their repositories describe limited/non-production prototypes; old age is not the same as archived status. | SSP · SAP · SAR |
| Control Plane Collie | A proof of concept combining cloud controllers, policy tools and the original Lula workflow. | Repository |
| Project SLEDGEHammer | A cloud-native compliance reference architecture and project charter. Read its intended capabilities as design work. | Repository |
| John Jediny OSCAL Static Site Playground | A Gatsby/React/USWDS starter for OSCAL-oriented websites. A development example rather than a supported general editor. | Repository |
| mocolicious OSCAL-Examples | OSCAL development examples using Angular, React, Flutter and MVC. | Repository |
| SHR Group iac2oscal | An infrastructure-as-code/OSCAL proof of concept. | GitLab project |
Names you may encounter in older directories: OMB OPAL; NREL-CYBER's oscal, oscal-atoms and oscal-cache; the original Big Bang OSCAL Component Generator; and the old Nix package path for oscal-deep-diff. Their original linked repositories or paths could not be retrieved during this update. The Awesome OSCAL index preserves the discovery context.
The original GSA/fedramp-automation repository link also could not be retrieved. Do not treat a legacy fork or a stale validation ruleset as current program authority.
These resources provide reusable content and reference material. They are not interchangeable with validation engines.
| Resource | What you can find | Use it for |
|---|---|---|
| NIST OSCAL releases | Versioned schemas and release artifacts. | Pin the schema release used by your toolchain. |
| NIST oscal-content | NIST control catalogs, profiles and examples. | Start with attributable source content. |
| OSCAL Content Registry | Published OSCAL documents and retrieval interfaces. | Find catalogs, profiles and component definitions; check each publisher and revision. |
| OSCAL Foundation FedRAMP resources | Baseline resources and example artifacts, including an SSP. | Develop integrations using sample package content. |
| OSCAL Foundation Pattern Library | Reusable implementation patterns. | Compare approaches to recurring modeling problems. |
| Australian ACSC ISM in OSCAL | ISM catalogs and profiles, including Essential Eight material. | Work with Australian security requirements. |
| CIS Controls OSCAL | CIS Controls content in OSCAL. | Reuse the publisher's machine-readable controls. |
| Cloud Security Alliance CCM bundle | Machine-readable CCM material, including OSCAL resources. | Explore cloud-control content and related mappings. |
| CMS machine-readable ARS | CMS Acceptable Risk Safeguards content. | Work with CMS-specific catalogs and profiles. |
| GovTech Singapore technical standards | Public policy and standards artifacts referenced by the OSCAL community. | Explore an international implementation. |
| CivicActions component definitions | Reusable component descriptions. | Learn how implementation information can be shared. |
| Red Hat component definitions and profiles | Community implementation and baseline artifacts. | Inspect examples, checking their revision and maintenance status. |
| Fathom5 SP 800-171 content | Community-maintained SP 800-171 OSCAL content. | Compare a community conversion with the original publication. |
| CyberESI CPRT OSCAL Catalog Library | OSCAL conversions of CPRT framework content. | Explore converted catalogs and their provenance. |
| SHR Group diagram examples | OSCAL relationship diagrams and advanced modeling examples. | Discuss how documents and components relate. |
For formal definitions, use the NIST OSCAL reference. A schema describes the document model; a control catalog supplies framework content; a profile selects and tailors that content. Check them separately.
Start with one representative document from your own workflow. Include the extensions, links and imports you actually depend on.
| Check | What a useful answer looks like |
|---|---|
| Document models | The exact models supported for import, editing, validation and export. A tool may support SSPs but not assessment results or mapping collections. |
| OSCAL release | The specific model versions tested by the tool. The application's own version number is a separate identifier. |
| File formats | Explicit JSON, XML and YAML support. Accepting JSON does not imply XML conversion or faithful round trips. |
| Preservation | Your UUIDs, props, namespaces, links, back matter and extensions survive import and export. |
| Profile handling | The tool can resolve the profiles and imported documents used in your workflow, with clear behavior for unavailable imports. |
| Data processing | You know whether the document stays in the browser, is processed on your own server, or is sent to an external API or AI provider. |
| Review and provenance | You can identify which source, person or automation produced a change, and review it before use. |
| Licensing and maintenance | The software license permits your intended use, and its status is appropriate for your deployment. Public source alone does not establish either. |
| Validation layer | What it checks | What it does not establish |
|---|---|---|
| Schema validation | Document structure, required fields and schema-defined types and shapes. | All OSCAL semantics, correct references across a package or compliance with a program. |
| Core OSCAL semantic constraints | Additional model rules, such as permitted vocabularies, uniqueness and applicable reference constraints. | That the described controls are implemented or the evidence is sufficient. |
| Program-specific checks | Additional rules and expectations of a particular program, baseline or receiving system. | Authorization, certification or acceptance solely because a tool returned a passing result. |
Cross-document checks and profile resolution also need explicit coverage. A file can satisfy its schema while pointing to a missing baseline or referring to controls outside the selected profile.
For our public browser/API scope and the separate toolkit research, see Secani's validator, API documentation and the semantic-validation report.
Copy this synthetic OSCAL 1.2.2 catalog. It contains one illustrative control and no customer or framework content.
{
"catalog": {
"uuid": "32c3619a-1bb3-4c43-967d-b4df6291c621",
"metadata": {
"title": "Example access review catalog",
"last-modified": "2026-10-19T07:45:00Z",
"version": "1.0.0",
"oscal-version": "1.2.2"
},
"controls": [
{
"id": "example-1",
"title": "Review access permissions",
"parts": [
{
"name": "statement",
"prose": "Review access permissions at defined intervals and record the result."
}
]
}
]
}
}
This exercise demonstrates structure checking and document viewing. The example passing validation does not prove that access reviews take place.
Yes. The Easy Dynamics OSCAL Viewer provides a browser reading interface, and the Secani OSCAL Validator provides browser-local JSON schema checks. The open-source Java CLIs provide additional processing workflows when installed.
Examples include Trestle, go-oscal, Roscal, the Easy Dynamics Viewer, OSCAL Hub and the NIST tooling. Check the linked license for the project you select. Source-available tools such as the NTT DATA Audit Automator, and repositories with noncommercial restrictions such as oscal4neo4j, need separate consideration.
Some commercial tools and migration projects support document import or conversion. You still need to map the source information to the target model, resolve missing information and review the generated content. A file conversion cannot establish facts that were absent from the original documentation.
No. A passing result only covers the rules that validator actually checked. OSCAL structure, semantic constraints, current program requirements, evidence quality and the authorization decision are different questions. Use the receiving program's current requirements alongside the tool documentation.
They still appear in search results, tutorials and community directories. Keeping their names visible with status and successor links helps you recognize an old dependency and locate an appropriate current alternative.
Check OSCAL.io, Awesome OSCAL, the GitHub OSCAL topic and NIST workshops. To suggest an addition to this directory, contact Secani with the project URL, documented OSCAL capability and current availability.

OSCAL · July 16, 2026 · 6 Min.
With RFC-0024 and the Consolidated Rules 2026, FedRAMP makes structured authorization data mandatory. The deadlines are staggered – the direction is unambiguous.

OSCAL · July 14, 2026 · 7 Min.
OSCAL turns compliance documents into structured data: eight document models, three formats, and an ecosystem that is becoming the standard for regulation.

OSCAL · July 26, 2026 · 20 Min.
OLIR provides mapping content and governance. OSCAL provides the machine-readable structure for using those mappings in gap analysis, evidence reuse, and change-impact workflows.
Secani connects scopes, evidence, tasks, and AI agents in one shared workspace.