Decima Systems
Menu / Explore Decima

Method / Before, during and after the assessment

Evidence first.
Permission always.

A closer look at the testing method and engagement process. Every assessment starts with an agreed scope and ends with a record that can be inspected.

02 / Product design

Purpose-built for security work

01

Specialist models

Chosen for the task. Tested in the tools.

We’re developing a catalog of open-weight models with reduced refusal behavior and training for authorized security work. Each variant must earn its place through evaluations of finding quality, tool use, review effort and cost. The goal: customer choice among tested options, with a dependable default.

02

An attack harness

From a hypothesis to reproducible evidence.

The core design puts a model agent in an isolated Kali-style environment with curated security tools. A purpose-built harness will coordinate planning, execution, verification and evidence capture. We optimize for a completed assessment: what it finds, what it misses, and what it costs to review.

03

Reports worth reading

For the board. For the fix.

We’re designing daily PDF reports with the care of a premium publication: confident typography, clear charts and an executive narrative backed by verified technical evidence. Alongside the live findings view, each edition will show business impact, fixes, relevant ISO control mappings and actual test dates. Planned Vanta and Drata connections will deliver reports and remediation evidence into your compliance workflow.

04

Defined boundaries

Your scope. Your data requirements.

Each engagement must define permitted targets, testing windows, stop conditions and data handling. Self-hosted inference is the intended default; customer-perimeter deployment is a separate development track. Model hosting, tool output, evidence storage and operator access all belong in that agreement.

05 / Getting started

Your first assessment. Step by step.

A clear plan, a proposal worth presenting, and your company’s approvals before testing begins.

Current stage

Engagement planning, PDF proposals, domain verification, recorded sessions and sample reporting are available. Assessment execution requires an approved engagement, account funds and an available worker. Direct Cloudflare connection, DocuSign and completion emails remain planned integrations.

01

Define the engagement

Tell us about your organization and the security questions you want answered. Explore the demo and sample report at any time.

02

Set scope and budget

Describe the proposed systems and exclusions, choose a monthly planning allocation and request a testing frequency. We confirm the feasible coverage and final quote together.

03

Take the proposal to your board

Download a designed PDF with your scope, budget, reporting examples and next steps. Share it with your own decision-makers, then record the internal budget approval.

04

Verify domain control

Add a verification record with your existing DNS provider. A direct Cloudflare connection is planned. Verification can happen while your proposal is under review; it does not authorize testing.

05

Complete the agreement

The engagement agreement brings the final scope, service terms and testing authorization together for an authorized executive to sign. Confirm exclusions and third-party permissions before active work.

06

Review and activate

Confirm the exact price, assessment scope and first testing window when delivery is ready. The assessment brings findings to your console and reviewed reports to your team, at the agreed cadence.

Next

See yourselffrom the other side.

Create your workspace now. Bring one application and your reporting requirements. We’ll agree testing cadence, scope and the approvals your organisation needs to activate.