Independent project · AI-assisted · verified build · synthetic data

My cyber-exposure architecture projectSecurity architecture · engineering · automation

I make closure
verifiable.

I developed Exposure Control with AI assistance to explore risk scoring, ownership, remediation, and validation. The data is synthetic. This is independent, non-production work.

Optional review tools
Implementation checks and limits
Explore the six-stage architecture
  1. SignalsFragmented findings
  2. Canonical ModelNormalized records
  3. Business ContextApps, assets, owners
  4. PolicyScored priorities
  5. OwnerOwner and team routing
  6. EvidenceValidated closure

SIMULATED EXAMPLE · EXP-1031

From public listing to validated closure.

Modeled priorityP0Synthetic data. No live telemetry.
  1. Detect

    analytics-archive-sim

    Public object listing

  2. Route

    Data Platform

    Priya D.

  3. Remediate

    Removed the public policy

    added a preventive control

  4. Validate

    Configuration diff

    anonymous-access retest

SIMULATED OUTCOMERemediated ·

Without valid, current evidence, work stays open.

Explore the synthetic records
FICTIONAL BANKING DATASET

100 applications. 1,000 assets. 20 teams.

I use Atlas Meridian, a fictional banking dataset, to model applications, assets, teams, ownership gaps, and source quality. It contains no employer or customer data.

100
Applications
1,000
Assets
20
Engineering teams
~10,000
Correlated exposures

Validated synthetic scale model; not a production benchmark. The dashboard makes all 10,000 synthetic records filterable and keeps 12 representative cases for readable detail.

THE CONTROL PATH

From a finding to an owner and a validation result.

A source finding is normalized, enriched with business context, evaluated through policy, routed to an accountable owner, tracked through remediation, and only closes when current validation meets the closure conditions. A failed gate returns the work.

Swipe to follow all five stages →
Exposure Control control pathFive stages connect detection, deterministic prioritization, accountable ownership and routed remediation, validation, and closure. Failed validation returns work to remediation.INPUT & POLICY BOUNDARYACCOUNTABLE REMEDIATIONVALIDATION GATE1DETECTNormalized signal fromscans and file input2PRIORITIZEContextual risk andgoverned priority3ROUTE & REMEDIATEOwner and team resolved;work routed and tracked4VALIDATEFreshness and tenantidentity checked5CLOSEOnly after evidencemeets closure checksGATE FAILS: RETURNTO TRACKED REMEDIATIONGATE PASSES: CLOSEWITH NEWER EVIDENCE
DEMONSTRATION BOUNDARY

Atlas Meridian is the fictional banking dataset for this model. It is synthetic, non-production, and not real bank data or customer telemetry.

PRODUCTION BOUNDARY

A real deployment requires separately permissioned identities, authoritative scanner retests, operating controls, and measured reliability.

WHAT I BUILT

Schemas, scoring, routing, and closure checks.

I used AI assistance to develop the lifecycle, schemas, scoring, adapters, ownership routing, persistence, validation gates, and tests. This project does not represent unaided coding expertise or a production client implementation.

01 / MODELCanonical schemas and workflow invariants
02 / DECIDEDeterministic contextual risk and a versioned remediation-priority policy
03 / ACTOwnership resolution, remediation routing, and an idempotent GitHub Issues adapter
04 / STORESQLite persistence and a PostgreSQL adapter with forced tenant row-level-security policies
05 / ASSURETests, scanners, workflow permissions, and deployment references
WORKING TODAY

Runnable reference implementation

Local-only CSV ingestion, deterministic risk scoring, accountable routing, a GitHub Issues adapter, two persistence adapters, repository scanners, a dashboard, and a synthetic lifecycle demo.

PRODUCTION EXTENSION

Authoritative sources and operations

IAM, EDR, CSPM, CMDB, Jira, and ServiceNow integrations are extension points for production integration. Production also needs recovery, security, reliability, and scale controls.

ROUTING CONTROL

No silent assignment

Asset-to-application and application-to-team context resolve ownership. Missing, stale, or conflicting ownership is held for governance review and escalation instead of being routed silently.

Inspect the technical architecture Try browser-local prioritization
IMPLEMENTATION REVIEW

Review the dashboard, model, and limits.

I use synthetic data so you can inspect the design without employer or customer information.

CONTROL / LIFECYCLE

Working synthetic lifecycle

The public decision dashboard demonstrates the finding-to-closure model with synthetic systems, owners, remediation states, and validation records.

Demonstrated
CONTEXT / ATLAS

Fictional banking dataset

Atlas Meridian is a fictional, non-production enterprise context used to reason about applications, assets, teams, owners, source quality, and decision routing.

Modeled
ASSURANCE / VERIFIED

Quality gates completed

The portfolio build, type, lint, automated-test, dependency-audit, and browser checks completed successfully before publication.

Verified
BOUNDARY / CONTROLLED

Synthetic data and private source

Synthetic data demonstrates the design, implementation source stays private, and the dossier states what production adoption would require.

Bounded
PROJECT FIT

How I approach the work.

Use the project to discuss how I model findings, explain remediation priorities, assign owners, and check closure evidence.

Alfe Corona, creator of the Exposure Control cybersecurity architecture portfolio
Developed with AI assistance byAlfe CoronaRisk scoring · remediation routing · closure validation