Ownership and risk
Define authorized tenants, asset owners, privacy limits, vendor dependencies and written incident responsibilities.
Documentation stagedCHYPHNX / Identity security observability
ARCHITECTURE PREVIEW — NOT LIVE TELEMETRY
PROTECTION BEGINS
WITH EVIDENCE.
One security command center for identities, assets, endpoint signals, network defenses and recovery. Source code, control mapping and tests are staged; personal accounts and devices are not being scanned or monitored.
No password-manager contents, MFA codes, student account data or private security logs are present on this page.
SECURITY OPERATIONS / STATUS
SOURCE VERIFIEDCODE TESTEDNot production protection
IDENTITY FEDERATIONNOT ACTIVE
AUTHORIZED DEVICE SENSORSNOT CONNECTED
VULNERABILITY INTELLIGENCEADAPTER STAGED
SSO.CPX.AGENCYNOT ACTIVATED
System health follows evidence; unavailable sensors are never counted as zero attacks.
FRAMEWORKNIST CSF 2.0
SECURITY FUNCTIONS6 MAPPED
CONTROL PLANS12 DOCUMENTED
ACTUAL DETECTION COVERAGENOT VERIFIED
01 / Risk governance
SIX FUNCTIONS.
ONE CONTROL SYSTEM.
The six Cybersecurity Framework functions describe objectives, not government certification. Implementation requires verification against operational evidence.
Know the inventory
Keep personal, CPX, academic and external business identities independent; inventory actual apps and device agents.
Connector ledger in sourcePasskeys and least access
Validate OAuth state, issuer and consent; keep password managers native and preserve third-party MFA.
Policy code testedAttested signal coverage
Build detections from signed real sensors, not invented malware, spyware, tracking or intrusion totals.
Schema and rule code testedControlled containment
Triage verified alerts, preserve evidence and revoke tokens only through owner-authorized workflows.
Incident playbook stagedRestore and continue
Maintain independent break-glass access and encrypted Google Drive/Proton Drive recovery copies.
Restore test pending02 / Source of truth
NO SIGNAL.
NO FALSE CLAIM.
Actual results will populate only after authorized devices, providers and applications report through a verified backend.
01
Identity and MFACloudflare Access / approved first-party identity server
NOT CONNECTED02
Email phishing and malwareApproved Gmail / Microsoft / provider-native security signals
NOT CONNECTED03
Endpoint malware and spywareUser-authorized Android and desktop security products
NOT CONNECTED04
Network trackers and malicious DNSOwner-controlled browser and network blocking logs
NOT CONNECTED05
Software and repository vulnerabilitiesGitHub source tests; SBOM and package exposure checks pending
SOURCE TESTS ONLY06
Encrypted backup and restoreActual isolated restore evidence from both destinations
NOT VERIFIED03 / Public threat intelligence
CURRENT STANDARDS.
VERIFIED FINDINGS.
CISA KEV + NIST NVD
Read-only adapters validate official public vulnerability records, timestamps, source freshness and bounded NVD pagination. A staged six-hour GitHub schedule begins only after approved merge.
A public CVE is not evidence that CPX assets are compromised. Matching requires a verified component inventory, versions, applicability and review.
AUTHORIZED SECURITY TESTING
Verify before trusting.
Local OAuth abuse cases, replay attacks, privilege isolation and malformed event inputs are tested. A live penetration test is not claimed, and no third-party provider or university system is targeted.
OWASP ASVS 5.0.0 / NIST SP 800-61 Rev. 3Operational analytics pending
When signed sensors are connected, the control plane can summarize verified daily and weekly events, source completeness and matched before/after trends. Until then, malware, spyware and tracker detection outcomes remain unknown—not zero.