Audience: Administrators and implementation teams.

Configuration

Core runtime settings, policies, secrets, authentication, RBAC, SIEM, and metrics.

Guide

Configuration Sources

GeoCordon uses process-local environment variables and customer-managed files for policies, keys, audit storage, identity providers, SCIM, approvals, SIEM, and HA.

Authentication and RBAC

Admin APIs use authenticated sessions and permission checks. Built-in roles determine whether users can view evidence, manage users, inspect operations, or generate support bundles.

Optional Integrations

Optional integrations such as SIEM, SCIM, identity providers, approvals, and HA fail closed when enabled with invalid configuration.

Authoritative Sources

These repository documents remain the source of truth for implementation details.

Dashboard and admin API

Admin routes, sessions, RBAC, and safe dashboard surfaces.

docs/DASHBOARD.md

GeoCordon includes a local administrator dashboard, authenticated admin APIs, and a customer-facing documentation portal.

Policy format

Policy files, registries, rule actions, and validation.

docs/POLICY_FORMAT.md

Milestone 3A defines the first strict policy file format for isolated policy loading and pure JSON transformation. Milestone 3B applies that same policy format to live non-empty proxy request bodies.

Security model

Authentication, RBAC, secrets, SIEM, HA, and fail-closed behavior.

docs/SECURITY_MODEL.md

Gateway is designed to reduce sensitive-data egress through deterministic proxy enforcement and auditable decisions. This model describes intended controls and explicit limitations.

Operations

Operational signals, incident categories, and troubleshooting paths.

docs/OPERATIONS.md

Operational procedures for customer-operated GeoCordon (Gateway). These runbooks assume the security and deployment baselines in `docs/PRODUCTION_HARDENING.md`, `docs/DEPLOYMENT.md`, and `docs/KUBERNETES.md`.