Skip to content
Cybercraft Labs
Services/Cybersecurity

Find it the wayan attacker would.

Penetration testing, red teaming, AI system security and infrastructure hardening — scoped against your real threat model and reported so your team can start fixing the same week.

Request an assessment
What we test

Seven ways in,
tested properly.

AI

AI systems
security

Three dedicated offerings for models, agents and the tooling around them.

01

Vulnerability
assessment (VA)

Clear visibility into exposed weaknesses across the estate, prioritised by risk and by how likely each one is to actually be exploited.

02

Penetration
testing (PT)

Validated attack paths that demonstrate real-world impact, so remediation order follows consequence rather than scanner severity.

03

Red team
engagements (RT)

A goal, a time box, and no map. We measure people, process and detection against realistic adversary behaviour and show you the whole chain.

04

Web & API
security testing

Authentication, authorisation and business-logic flaws — the high-impact class automated testing consistently misses.

05

Infrastructure &
cloud security testing

Misconfigurations and privilege-escalation paths across IAM, network boundaries and secrets handling. Most cloud incidents are configuration.

06

Purple
teaming

Offensive and defensive work run together, so detection accuracy and response time improve while we are still in the building.

07

Threat
modelling

What is actually worth attacking in your system, based on its design and your business context — before anyone writes a test plan.

AI security

Models fail in waysa scanner cannot see.

An LLM with tool access is an execution path. We test it as one — against the deployed system, its retrieval layer and its permissions.

01

AI / LLM security
assessment

Prompt injection, data-extraction paths, unsafe tool invocation, and misalignment with your security and privacy requirements. Tested against the deployed model and its tooling, not the vendor datasheet.

02

AI red
teaming

Goal-driven adversarial work against models, agents and the systems they can reach. We chain jailbreaks with real capability — retrieval, function calls, downstream services — and show the whole path.

03

AI security
testing

Continuous testing built into your pipeline: regression suites for known bypasses, evaluation of guardrail coverage, and checks that survive a model or prompt change.

Building with AI rather than defending it? We develop AI systems too.

AI engineering
Reporting

What a finding
looks like

Every issue arrives with the exploit path, the blast radius, and a fix your team can implement. Severity without a remediation plan is noise, so we do not ship it.

Critical issues are reported the day we find them.

FINDING — SAMPLECRITICAL
TITLE
Tenant identifier trusted from client payload
PATH
authenticated user → edit request → swap org_id → read another tenant's records
BLAST RADIUS
All customer records reachable by any logged-in account.
FIX
Derive tenant scope from the session server-side; add an authorisation test per endpoint.
RETEST — INCLUDED
Timeline
WEEK 00

Scope

Assets, access, threat model, rules of engagement. Fixed price agreed here.

WEEK 01–02

Testing

Active work with a live findings channel. Nothing waits for a document.

WEEK 03

Report & walkthrough

Ranked findings, fixes, and a session with your engineers to work through them.

WEEK 04+

Retest

We verify each fix and update the report. Included, not an upsell.

A breach is priced in millions, but it is authored much earlier — in a rushed release, an unreviewed dependency, a default left in place. That is where we work.

Bring us the partthat worries you.

Forty-five minutes with an engineer. We will tell you where your real exposure is and what it would take to close it — no obligation either way.

Book the call