Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacyΒ© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
enterprise-abac-gateway β€” Zero-trust reverse proxy and ABAC authorization gateway in Go with embedded OPA policy evaluation and distributed token revocation. | Kitploit
Tools/GitLabGitLab/kavryxdev-group/enterprise-abac-gateway
Authentication & AuthorizationDefensive ToolsWeb Proxies & InterceptionNetwork SecurityCloud SecurityIdentity & Access Management (IAM)
GitLabkavryxdev-group/enterprise-abac-gateway

enterprise-abac-gateway

Most Popular

View all β†’

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools β†’
Share

Zero-trust reverse proxy and ABAC authorization gateway in Go with embedded OPA policy evaluation and distributed token revocation.

View Repository
2612h 56m agoNot yet reviewed

πŸ›‘οΈ Enterprise Fine-Grained Attribute-Based Access Control (ABAC) Gateway

Go Version OPA Engine Redis Cache PostgreSQL NIST Compliance Latency SLA License

High-performance, zero-trust reverse proxy and authorization gateway built in Go with an embedded Open Policy Agent (OPA) engine, sub-5ms decision latency, real-time distributed token revocation via Redis Pub/Sub, and cryptographic tamper-evident audit logging.


πŸ“Œ Executive Overview

Modern cloud-native and multi-tenant platforms require authorization paradigms far more granular than static Role-Based Access Control (RBAC). In high-assurance environments, authorization must dynamically synthesize who the requester is (Subject), what action they seek to perform (Action), what data classification applies (Resource), and real-time operational context (Environment).

The Enterprise Fine-Grained ABAC Gateway acts as a centralized Policy Enforcement Point (PEP) and Policy Decision Point (PDP) fronting backend microservices. Engineered to comply with NIST SP 800-162 (ABAC), NIST SP 800-207 (Zero-Trust Architecture), and RFC 7519 (JSON Web Tokens), it eliminates authorization latency by compiling Rego policies directly into the Go process memory space, avoiding out-of-process network hops while maintaining distributed consistency across cluster instances.

🌟 Key Capabilities

  • ⚑ Sub-5ms Decision Latency SLA ($T_{\text{eval}} \le 5.0\text{ ms (p99)}$): In-memory attribute resolution and local policy compilation in Go via embedded OPA eliminate blocking database roundtrips during hot-path authorization.
  • 🎯 Four-Dimensional Vector Evaluation ($S, A, R, E$): Computes decisions dynamically across Subject (roles, tenant, clearance, MFA status), Action (verb, idempotency classification), Resource (classification, tenant owner, lifecycle tags), and Environment (client IP/CIDR, business hours, device trust posture).
  • πŸ”„ Real-Time Distributed Invalidation ($\le 100\text{ ms}$): Emergency token revocations (JTI) and role changes propagate immediately across all gateway instances via Redis Pub/Sub, updating in-memory LRU caches in under 100ms.
  • πŸ”’ Cryptographic Tamper-Evident Audit Chain: Every authorization outcome (ALLOW / DENY) is recorded in an append-only SHA-256 hash chain ($\text{Hash}n = \text{SHA-256}(\text{Hash}{n-1} + \text{Snapshot}_n)$) persisted asynchronously to PostgreSQL for SOC 2 Type II and ISO 27001 audit trails.
  • 🏒 Ironclad Multi-Tenant Isolation: Complete isolation between tenant organizations enforced cryptographically and logically at the route and policy layers, with default-deny fail-closed semantics.
  • 🚨 Emergency Break-Glass Protocol: Governed bypass paths for critical incidents with mandatory audit obligations and automatic tenant boundary containment.

πŸ“ System Architecture

The gateway is partitioned into an ultra-low latency Data Plane (HTTP Reverse Proxy & In-Memory PDP), an isolated Control Plane (Admin API for policy and revocation management), and resilient State & Persistence Tiers (Redis 7 & PostgreSQL 16).

Interactive Architecture Diagram (Archify)

System Architecture
Figure 1: High-level System Architecture diagram generated with Archify.
πŸ‘‰ πŸ” Click Here to Open Interactive Archify Diagram (Supports dark/light themes, clickable nodes, and deep component inspection)


Native System Architecture Map

graph TD
    subgraph Clients["Perimeter & External Consumers"]
        ClientApp["Client Applications (SPA / Mobile / Microservices)"]
        SecOps["SecOps & Admin Console"]
    end

    subgraph DataPlane["Enterprise Zero-Trust Gateway (:8080)"]
        direction TB
        AuthMid["Auth Middleware (JWT, JTI, Leeway)"]
        PEP["ABAC Interceptor (PEP Gate)"]
        Resolver["Attribute Resolver (S, A, R, E)"]
        OPA["Embedded OPA Engine (Rego Runtime)"]
        Proxy["Reverse Proxy (httputil)"]
        PubSubLis["PubSub Invalidation Listener"]
        AuditLog["Non-Blocking Audit Logger"]
        HashChain["SHA-256 Cryptographic Chainer"]
    end

    subgraph ControlPlane["Control Plane (:8082)"]
        AdminAPI["Admin API (Revocations & Health)"]
    end

    subgraph StateTier["Distributed State & Persistence"]
        Redis["Redis 7 (Vector Cache & Blacklist :6380)"]
        Postgres["PostgreSQL 16 (Ledger & Tenant DB :5433)"]
    end

    subgraph UpstreamTier["Target Services"]
        Upstream["Protected Upstream API (:8081)"]
    end

    ClientApp -->|"HTTPS + Bearer JWT"| AuthMid
    SecOps -->|"Admin Key Auth"| AdminAPI
    AdminAPI -->|"Publish JTI Revocation"| Redis
    Redis -.->|"Pub/Sub Channel (<=100ms)"| PubSubLis
    PubSubLis -->|"Invalidate Local LRU"| AuthMid

    AuthMid -->|"Verified Identity Claims"| PEP
    PEP -->|"Build Evaluation Context"| Resolver
    Resolver -.->|"Query Vectors"| Redis
    Resolver -->|"Vector (S, A, R, E)"| OPA
    OPA -->|"ALLOW / DENY (<5ms SLA)"| PEP

    PEP -->|"Authorized Traffic"| Proxy
    Proxy -->|"Reverse Proxy Forward"| Upstream
    PEP -.->|"Async Decision Record"| AuditLog
    AuditLog -->|"Hash Chain Generation"| HashChain
    HashChain -->|"Append-Only Immutable Write"| Postgres

Component Breakdown & Trust Boundaries

Download Tool