Security
Unclassified public capability briefKyon Dynamics keeps the public website intentionally unclassified and separates open inquiry from sensitive, CUI-aware, export-aware, or procurement-specific follow-up. Serious security or diligence conversations should begin with disciplined intake.
Explains the public rule set before a visitor, supplier, prime, or partner moves into controlled diligence.
Keeps classified, CUI, export-controlled, medical, procurement-sensitive, and proprietary material out of open website channels.
Use controlled follow-up for verification, records, legal review, supplier review, or sensitive business discussion.
Founder-led by a disabled veteran with Native American heritage, with public claims kept R&D-stage, qualification-first, and procurement-readable.
Officially licensed FEL and FFL manufacturer; product programs are presented as R&D or qualification-stage unless separately verified.
Documentation, traceability, controlled intake, and planned partner-review pathways built for prime-contractor review.
Public channels stay unclassified. Sensitive, CUI, export-aware, or procurement-specific discussions route through controlled follow-up.
Security
This page is written for unclassified public use. It sets expectations for visitors, partners, suppliers, primes, and public-sector readers before a controlled conversation begins.
Public Channel Boundaries
Do not send classified information, CUI, export-controlled technical data, weapon-system technical detail, proprietary customer information, or sensitive procurement material through public website channels.
Responsible Reporting
If you believe you found a security issue affecting the public website, contact Kyon with an unclassified summary, affected URL, browser context, and safe reproduction notes. Do not run intrusive testing, persistence, data access, or service disruption without written authorization.
Controlled Diligence
Prime-contractor, government, supplier, and strategic-partner diligence may require separate controlled channels, verification steps, and document handling procedures before sensitive details are exchanged.
No Public Exploit Detail
Security reports should avoid public disclosure, exploit code, sensitive screenshots, third-party data, or operational details. Keep the first contact concise and unclassified so the right follow-up path can be established.