DEMO // TFCS // INTERNAL-DEMO
TFCS

Trusted File Classification Specification

The single specification that governs how every file entering or leaving the F-35 MPE is classified, labeled, gated for releasability, and represented inside the SysML model.

Classification Levels

Levels recognized by the MPE

LevelNameHandling RuleTypical MPE Examples
UUNCLASSIFIEDOpen handling; still subject to OPSEC.Generic charts, public DAFIF, training scenarios.
CUICONTROLLED UNCLASSIFIEDNeed-to-know; encrypt at rest; CUI markings.Tail numbers, sustainment data, ALIS extracts.
SSECRETSIPRNet enclave; classified storage; two-person integrity for release.MDF threat libraries, datalink time slots, MADL plans.
S//NFTIER-2 // DEMO-LIMITEDUS persons only; no foreign disclosure; releasability gate must REJECT.US-only crypto material, USRL-only MDF variants.
S//RELSECRET // REL TO …Disclosure limited to named partners (PARTNER-GROUP, NATO, FMS-tailored).ACURL MDF variants, coalition mission packages.
TS//SCITIER-3 / SAMPLEJWICS only; SCIF; compartment caveats; separate key material.Selected intel-derived threat updates, sensitive sources.
Labeling Rules

Mandatory marking conventions

  • Every trusted file carries a header block + footer banner with overall classification.
  • Portion marks (U), (CUI), (S), (S//NF) on every paragraph / record / field.
  • Releasability line immediately under the banner: REL TO HOME, PARTNER-GROUP / DEMO-LIMITED / etc.
  • Handling caveats: ORIG-CTRL, PROP-INFO, DEMO-LIMITED, INTERNAL-DEMO — explicit, never inferred.
  • Originator + date of origin + declassification instruction (25X, OADR, source-derived).
  • Digital signature block: signer DN, cert chain, hash algorithm, timestamp.
  • Integrity hash (SHA-256+) bound to the signed manifest.
  • Container metadata mirrors the highest portion mark (high-water mark).
  • Coalition variants: separate file artifact per releasability; never overload one file.
Lifecycle

TrustedFile State Machine

⟦ SysML Snippet — TrustedFile lifecycle — modeled in 05_Behavior
Import Flow

Trusted File Import — Swimlanes

⟦ SysML Snippet — Activity diagram with partitions for Operator / Ground Security / Trusted Importer / Audit / UPC
SysML Mapping

Every TFCS concept → a SysML artifact

The TFCS is not a stand-alone PDF; it is generated from these model elements via DocGen.

TFCS ConceptSysML ArtifactCameo Package
Classification levelsEnumeration «Classification»12_Library
Releasability setEnumeration «Releasability»12_Library
Handling caveatsEnumeration «Caveat» (multi-valued)12_Library
Trusted file objectBlock «TrustedFile»04_Structure / L5
File lifecycleState Machine TrustedFile05_Behavior
Import flowActivity Diagram (swimlanes)05_Behavior
Releasability gateDecision Node + Guard expression05_Behavior
Labeling rulesConstraint Block + Parametric06_Parametrics
Security controlsRequirements (NIST 800-53 trace)09_Security
ICD with downstreamInterface Block «TrustedFileIF»08_Interfaces
Allocation to componentsAllocation Matrix07_Allocations
Evidence for ATODocGen template → TFCS PDF10_Verification
Releasability Gate

Guard expression (constraint block)

constraint block ReleasabilityGate {
  parameters
    fileClass        : Classification
    fileReleasable   : Releasability
    targetEnclave    : Enclave
    targetPartners   : Partner[*]

  constraint
    // 1. Enclave must dominate the file's classification
    enclaveLevel(targetEnclave) >= level(fileClass)
    // 2. DEMO-LIMITED ⇒ all partners must be US
    (fileReleasable == DEMO-LIMITED) ⇒ all(p in targetPartners | p == USA)
    // 3. REL TO X ⇒ partners ⊆ X
    (fileReleasable matches REL_TO(X)) ⇒ subset(targetPartners, X)
    // 4. TS//SCI ⇒ enclave == JWICS && SCIF == true
    (fileClass == TS_SCI) ⇒ (targetEnclave == JWICS) && SCIF
}