Skip to main content

We're starting with a problem we can make concrete.

We're cybersecurity leaders, operating in stealth and building our first product toward a larger vision.

We want to make security judgment reusable and keep it valid as software changes. That starts with understanding why a decision was made and what evidence supports it.

01 / Working today

Evidence-backed scanner triage

ICTX turns supported scanner findings into decisions you can inspect. It gathers evidence from code and configuration, applies deterministic rules, and states what still needs checking when the evidence is incomplete.

The product works today as a local triage and review workflow. Preserving reasoning across changes and revalidating earlier decisions are proposed next steps.

02 / Proposed next step

Keep the reasoning current

We want to preserve the reasons behind a decision and identify changes that require renewed review.

A finding might be dismissed because callers pass input through validation. If a later change bypasses that validation, the earlier decision needs another look.

Today's product does not track those changes or revalidate earlier decisions. This direction is proposed work that we want to test with teams doing this work.

03 / Longer-term direction

More important constraints, with clear limits

The same approach could eventually support security reviews, privacy requirements, and architectural constraints. Developers and coding agents could use current, scoped reasoning when changes are proposed and reviewed.

Each extension needs its own evidence and evaluation. We are keeping names, histories, and individual identities private while we build in stealth.