A Cyber Security Pilot project

Security work, gathered into one operating picture.

Daedalus brings organization access, domain health, local network scanners, Meraki audits, endpoint baselines, and evidence-backed reports into a shared workspace.

Platform overview

One workspace for recurring security work.

Daedalus is being built around domain-owned workspaces, clear authorization, dated evidence, and reports people can review and share.

01

Domain and email health

Passive DNS, SPF, DKIM, DMARC, and website checks preserve dated observations so teams can review changes over time.

02

Local NmapUI scanners

Run scanner instances on the networks they are responsible for. Authenticated outbound check-ins report status and scan evidence to the workspace.

03

Authorized website audits

Public-facing checks can be run against verified domains. Active checks are bounded by recorded authorization, with administrator overrides that expire.

04

Meraki reporting

Administrators connect a Meraki organization with an API credential to collect workspace-scoped inventory and generate audit reports.

05

CIS endpoint baselines

Downloadable profiles and endpoint results support baseline scoring, historical review, and ongoing alignment work for current macOS releases.

06

Reports and change history

Generate PDFs from saved evidence, see generation progress, and compare new observations with earlier results.

Access model

Each organization controls its own membership.

A Google identity can belong to multiple workspaces, with a separate role in each. New workspaces begin with an administrator. Domain ownership can be confirmed with a DNS TXT record; while verification is pending, the workspace remains in a time-limited probation state. Sharing access to an existing workspace requires its administrator's approval.

Authorization stays visible.

Website auditing scopes and time-limited administrator overrides are recorded so that an audit has a clear owner and expiration.

How it fits together

Static website, separate application.

The CSP marketing pages and Daedalus product overview can be served by GitHub Pages. The signed-in product stays on an application host with persistent storage.

GitHub PagesPublic CSP marketing pages and project overview.
Daedalus serviceSign-in, tenant APIs, history, integrations, and report jobs.
Organization workspacesRoles, credentials, evidence, audit history, and reports.
Local scannersCustomer-managed NmapUI instances connect outbound.
Project status: active pilot.

Features are under continued validation. Production operations, recovery exercises, integration credentials, and security-profile maintenance need ongoing review. GitHub Pages only serves static files; it does not host the application backend or customer data.