M-26-14 Federal Logging Reference Architecture Viewer

Viewer for the OMB M-26-14 Federal Logging Maturity Model — Elastic Stack reference architectures for Levels 1-4.

SecurityJavaScript · CSSGitHub @elasticOnlineOwner unconfirmed

Visit project GitHub

Have you tried it? One tap is enough. No sign-in needed.

Availability: Online; 30-day uptime 100%
Latest code update: Oct 8; Active repository
Latest version: None
Contributors: 5; Forks 2
Listed on nomorevibe: Oct 6; Repository created June 2026

Languages

JavaScript 98.5%
CSS 1.1%
Dockerfile 0.2%
HTML and others 0.2%

Updates0 updates

All

No updates detected yet. GitHub releases will appear here.

Comments

Newest first

···

GitHub issue delivery settings

Checking sign-in status.

Loading comments.

README

Elastic M-26-14 Logging Readiness Package (site)

React + Vite static site. npm install, npm run dev to work locally, npm run build to produce dist/. Vercel builds from main with the default command; vercel.json rewrites every path to index.html.

Build flags

Variable	Effect
`VITE_ENABLEMENT=on`	Mounts the internal field-enablement pages (`/enablement`, `/enablement/sales`, `/enablement/sa`) and turns the header logo into their entry point. Off by default, so the deployed customer build ships no route to them (design call DC-8, LRA change review). Set it for an internal deploy or a local `npm run dev`; never in the Vercel production environment.

Vite inlines the value at build time; the pages are absent from the bundle's route table, not hidden behind a redirect.

Capabilities page data

/capabilities is built from two files, cross-checked by scripts/check-catalog.mjs before every dev and build (also npm run check):

File	Source
`src/data/assetCatalog.json`	Generated by the pack: `python3 tools/gen-asset-catalog.py --out <this repo>/src/data/assetCatalog.json --kibana-env <env file> --host-var PUBSEC_KIBANA_HOST --key-var PUBSEC_API_KEY`. The `--kibana-env` arguments resolve the demo cluster's saved-object ids (detection rules are minted at install; the osquery pack too), so links open the right object. The key is read from the env file and never written anywhere. Regenerate after every pack change; the check fails the build if a capability names an asset that no longer ships or a shipped asset no capability describes.
`src/data/capabilities.js`	Hand-authored: each capability's text, the asset ids that contribute to it and the dashboard screenshots to show.
`public/screenshots/<dashboard id>.png` and `thumbs/<id>.jpg`	Captured from the demo cluster through the Kibana reporting API (`POST /api/reporting/generate/pngV2` with a `DASHBOARD_APP_LOCATOR` job, 1600 x 1200 preserve-layout, 7d for operations views, 30d for posture views, 90d for inventory views), then `sips -Z 640 -s format jpeg` for the thumbnail. All 21 dashboards are captured (2026-09-21, after LRA change-review items R-89 and R-94 were applied live and the R-97 drilldown fixes re-uploaded). Recapture a dashboard whenever its panels change and keep the same file name; the capability's `shots` list references the id.

Read the full README ↗

README

Elastic M-26-14 Logging Readiness Package (site)

Build flags

Variable	Effect
`VITE_ENABLEMENT=on`	Mounts the internal field-enablement pages (`/enablement`, `/enablement/sales`, `/enablement/sa`) and turns the header logo into their entry point. Off by default, so the deployed customer build ships no route to them (design call DC-8, LRA change review). Set it for an internal deploy or a local `npm run dev`; never in the Vercel production environment.

Vite inlines the value at build time; the pages are absent from the bundle's route table, not hidden behind a redirect.

Capabilities page data

/capabilities is built from two files, cross-checked by scripts/check-catalog.mjs before every dev and build (also npm run check):

File	Source
`src/data/assetCatalog.json`	Generated by the pack: `python3 tools/gen-asset-catalog.py --out <this repo>/src/data/assetCatalog.json --kibana-env <env file> --host-var PUBSEC_KIBANA_HOST --key-var PUBSEC_API_KEY`. The `--kibana-env` arguments resolve the demo cluster's saved-object ids (detection rules are minted at install; the osquery pack too), so links open the right object. The key is read from the env file and never written anywhere. Regenerate after every pack change; the check fails the build if a capability names an asset that no longer ships or a shipped asset no capability describes.
`src/data/capabilities.js`	Hand-authored: each capability's text, the asset ids that contribute to it and the dashboard screenshots to show.
`public/screenshots/<dashboard id>.png` and `thumbs/<id>.jpg`	Captured from the demo cluster through the Kibana reporting API (`POST /api/reporting/generate/pngV2` with a `DASHBOARD_APP_LOCATOR` job, 1600 x 1200 preserve-layout, 7d for operations views, 30d for posture views, 90d for inventory views), then `sips -Z 640 -s format jpeg` for the thumbnail. All 21 dashboards are captured (2026-09-21, after LRA change-review items R-89 and R-94 were applied live and the R-97 drilldown fixes re-uploaded). Recapture a dashboard whenever its panels change and keep the same file name; the capability's `shots` list references the id.

Read the full README ↗

M-26-14 Federal Logging Reference Architecture Viewer

Languages

Updates0 updates

Comments

M-26-14 Federal Logging Reference Architecture Viewer

Languages

Updates0 updates

Comments

Do you operate this project?

Introduction

README

Elastic M-26-14 Logging Readiness Package (site)

Build flags

Capabilities page data

README

README

Elastic M-26-14 Logging Readiness Package (site)

Build flags

Capabilities page data

M-26-14 Federal Logging Reference Architecture Viewer

Languages

Updates0 updates

Comments

Trending in Security

M-26-14 Federal Logging Reference Architecture Viewer

Languages

Updates0 updates

Comments

Trending in Security

Do you operate this project?

Introduction

README

Elastic M-26-14 Logging Readiness Package (site)

Build flags

Capabilities page data

README

README

Elastic M-26-14 Logging Readiness Package (site)

Build flags

Capabilities page data