PROGRAM / BLACK SWAN NETCONTROLLED INTRODUCTION

Dedicated communications architecture

Mission communications.
Reduced trust surface.

A proposed dedicated secure-communications appliance and customer-controlled delivery architecture for high-consequence teams.

Request architecture brief Review the concept

Seeking government, integrator, critical-infrastructure, and regulated-enterprise design partners for unclassified and CUI evaluation pathways.

01No phone-number identity
02Customer-controlled delivery
03Dedicated endpoint posture
04Security case as product

00 / DEFINITION

What is Black Swan Net?

A dedicated secure communications appliance—not another consumer chat account.

Black Swan Net is a proposed purpose-built endpoint and delivery architecture for government, critical-infrastructure, regulated-enterprise, and other high-consequence teams. The concept binds identity to dedicated devices, supports direct endpoint delivery, and provides an optional customer-controlled path for asynchronous delivery.

The program is in concept development and design-partner discovery. It is not currently certified, government-approved, or authorized for classified information.

01 / SITUATION

The dependency problem

Encryption is available.
Control is fragmented.

High-value conversations still depend on consumer endpoints, cloud identities, opaque service operators, uncontrolled file viewers, push systems, and infrastructure the customer may not own.

Black Swan Net is being developed as an appliance and operating model—not another chat account. The objective is to make identity, delivery, software provenance, and residual risk visible enough to test.

Cloud identity

Phone numbers, email addresses, SIMs, and vendor accounts are not intended to serve as cryptographic identity roots.

General-purpose endpoints

Browsers, app stores, cloud backup, and ordinary document viewers expand the attack surface around a protected conversation.

Provider custody

Directories, queues, recovery paths, and administrative control planes can concentrate operational trust in the service operator.

Invisible trade-offs

“Sent,” “deposited,” “delivered,” and “read” are different states. Mission users should not have to guess which one occurred.

DIR / PUBLIC BRIEFS

Crawlable program record

Start with the mission question.

These public briefs describe the concept, evaluation boundaries, and frequently asked questions without publishing confidential implementation details.

BRIEF / 01

Secure communications appliance

Device-bound identity, direct and customer-controlled delivery modes, message-state semantics, and residual risk.

Read architecture brief

BRIEF / 02

Government evaluation path

Commercial, CUI, and classified/NSS profiles; RMF and ATO boundaries; and evidence expected for an exact configuration.

Review evaluation path

BRIEF / 03

Program FAQ

Direct answers on current status, metadata, endpoint compromise, offline delivery, certification, leadership, and design partnerships.

Open program FAQ

02 / ARCHITECTURE

Control plane separated from content

Your endpoints hold identity.
Your organization controls delivery.

ENDPOINT / ALPHA Hardware-bound identity Dedicated device posture
Explicit peer verification

DIRECT MODE Authenticated encrypted path Both endpoints available

ENDPOINT / BRAVO Pinned peer identity Dedicated device posture
Honest receipt states

CUSTOMER AUTHORITY Policy, configuration, revocation Administration alone is not intended to decrypt content.

CUSTOMER DELIVERY PATH Optional asynchronous mailbox Opaque, expiring envelopes. Deposit does not mean delivery.

ASSURANCE EVIDENCE SBOM, provenance, test artifacts Reviewable releases and operating procedures.

MODE / DIRECT

Minimize infrastructure.

Ciphertext remains queued on the sender when the recipient is unavailable. Delivery requires an authenticated endpoint acknowledgment.

Overlapping availability required

MODE / CUSTOMER PATH

Enable asynchronous operations.

An optional customer-controlled delivery component is intended to hold expiring, endpoint-encrypted envelopes without conversation keys.

Infrastructure trade-offs remain visible

03 / MISSION PROFILES

Claims do not cross boundaries

One product family.
Three distinct assurance paths.

A commercial security review, a validated component, a product evaluation, and an agency authorization are not interchangeable.

INITIAL MARKET

Commercial privacy

Boards, legal and M&A teams, investigations, executive protection, family offices, and crisis-response teams.

ASSURANCE DIRECTIONIndependent mobile and cryptographic review

DESIGN-PARTNER PATH

Regulated / CUI

Federal contractors, critical infrastructure, regulated enterprises, and customer-defined unclassified missions.

ASSURANCE DIRECTIONNIST SP 800-171 / 800-53 mapping, FIPS boundary planning, customer ATO support

SPONSOR-DEFINED

Classified / NSS

A separate, multiyear pathway that would require a government sponsor, an approved complete architecture, and exact operating constraints.

ASSURANCE DIRECTIONNIAP / Common Criteria, CNSA, CSfC or other sponsor-directed path, RMF authorization

04 / ASSURANCE

Built for the security review

Evidence is part of the product.

The objective is to supply the artifacts an Authorizing Official, ISSM/ISSO, security control assessor, records officer, COMSEC stakeholder, integrator, or independent evaluator needs to examine a defined configuration.

RMF
ATO
NIST 800-171
NIST 800-53
FIPS 140-3
NIAP / CC
CSfC
CNSA
STIG / SRG
SBOM
SSDF
CJIS*
CMMC*

* Applicability depends on the customer, contract, information type, system boundary, and exact deployed configuration.

01
System boundary
Architecture, trust assumptions, data flows, inherited controls, and residual risk.
02
Build provenance
Component inventory, SBOM, signed releases, update policy, and supply-chain evidence.
03
Verification record
Protocol review, test vectors, penetration findings, remediation, and operational exercises.
04
Mission CONOPS
Provisioning, custody, loss, revocation, records, retention, offline behavior, and incident response.
05
Continuous assurance
Configuration control, vulnerability handling, monitored changes, and reassessment triggers.

Claim boundary // current program status

Precision before promotion.

Black Swan Net is a proposed product under development. It is not currently represented as certified, government-approved, authorized for classified information, equivalent to a SCIF, anonymous, “unhackable,” or free of metadata and endpoint risk.

OPERATING RULE A component validation does not validate the whole product. A product evaluation does not authorize a customer deployment. The customer’s Authorizing Official controls the ATO for the exact system.

Gene Avakyan, founder and project lead of Black Swan Net

PROJECT LEAD / 01MIAMI, USA

05 / LEADERSHIP

Founder & project lead

Gene Avakyan

Aerospace engineer · Technology strategist · Enterprise systems architect

Gene Avakyan has spent three decades architecting enterprise systems that handle billions in transactions, including procurement and contract-management platforms supporting more than $13 billion in contracts for the City of Los Angeles and the Federal Aviation Administration.

He is an InfraGard member and the co-founder and CEO of VUGA Group. His work includes the City of Los Angeles LABAVN contract platform, the L.A. City Attorney’s T.O.U.G.H. law-enforcement system, the Heavy1 full-size unmanned electric spray aircraft, and defense unmanned-platform engineering for the United States and allied countries.

Gene holds a degree in Aerospace Engineering from UCLA and an MBA from Pepperdine University.

UCLA
Aerospace Pepperdine
MBA InfraGard
Member 30 years
Systems

Full biography and work

DESIGN PARTNER CHANNELUNCLASSIFIED INITIAL CONTACT

Mission discovery begins here

Define the threat.
Then define the system.

Request a controlled architecture briefing, paid design-study discussion, integrator conversation, or unclassified/CUI pilot scoping session.

Open a channel Verify project leadership