Aplex COMPUTER
SYSTEMS
PAGE ABOUT
[email protected]

First we show youwhat is open

Two lines of work, one logic. Find what is already open in your defences, and close it inside the process so that the decision stays with a human.

TELL US WHY YOU CAME

THE WHOLE PAGE ADAPTS: THE LIST, THE STEPS, THE EXAMPLES. YOU CAN SWITCH AT ANY TIME FROM THE HEADER.

SCAN · FOUND 0  / CLOSED 0
AN OPEN PERIMETER · THE SWEEP FINDS THE GAPS AND CLOSES THEM
CLASSES OF FINDINGS
10_
DECISION POINTS FOR AI
8_
POINTS IN A PILOT
1–2_
DATA LEAVING YOU
0_
01 / WHAT WE FIND
IN THE LIST 10

Ten classes of findings we meet most often

These are classes, not your network. Click a row and the breakdown appears: where this usually sits and what we do about it.

HOW OFTEN
CLASS OF FINDING

THE SCALE IS OUR ESTIMATE FROM PAST ASSESSMENTS, NOT A MEASUREMENT IN YOUR NETWORK.

BREAKDOWN / 01ALMOST ALWAYS
HOW OFTEN WE MEET THIS CLASS1 — 5
A leaver whose access stayed
WHERE WE USUALLY FIND IT
Accounts in email, VPN and admin panels outlive the person: the departure went through HR but not through the systems.
WHAT WE DO
We reconcile the list of people with the list of accounts, show the gap, and agree who closes access and on what trigger.

THE BREAKDOWN DESCRIBES A CLASS, NOT YOUR SYSTEM. WHAT IS OPEN AT YOUR END BECOMES VISIBLE ONLY AFTER A CONTRACT AND ACCESS.

02 / WHERE THE TWO LINES MEET

Finding it
is not enough

A finding is closed inside a process, and the process lives with people: in email, in logs, in tickets, in a policy read once a year. The second half of our work is to connect those tools and leave the last word to a human.

A FINDING WITHOUT A PROCESS
stays in the report
A PROCESS WITHOUT A FINDING
closes the wrong thing
TRACK 01 · WHAT WE FOUND
TRACK 02 · WHAT CLOSED IT
NODE · A HUMAN YES
03 / HOW IT GOES
STEP 01
01
Reconnaissance and code review

We look from outside, from inside and into the code, within an agreed window. The duty shift knows about the work in advance.

STEP 02
02
The register of findings

For every finding we write down the class, where it sits, what it threatens and what happens if it is left until the next assessment.

STEP 03
03
Closing and a second pass

A plan by priority, help with the fix, and a repeat check of the same places.

04 / WHAT WE NEVER DO
PROHIBITIONS 4
WE DO NOT
WHAT WE DO INSTEAD
01
Emails sent by the AI
The AI puts a draft in the queue. A human sends it, with their own hand and under their own name.
02
Granting rights and access
Your administrator changes permissions on request. The AI only shows who is asking for what.
03
Your texts in someone else's environment
The AI model learns and runs on your side. Neither logs, nor policies, nor correspondence leave it.
04
Testing without permission
We work within an agreed window and under written authorisation. The duty shift knows in advance.

THESE ARE NOT PROMISES ON A WEBSITE. WE PUT ALL FOUR IN WRITING BEFORE THE WORK STARTS, AND THEY DO NOT CHANGE ALONG THE WAY.

05 / NEXT STEP

So where do we start

The first step is the same either way: a conversation with no access to your systems. What comes next depends on what you choose.

01 / SECURITY
Show us
what is open

A conversation, then a short risk note, then a proposal with scope and timing.

[email protected]
02 / AI MODELS
Put the AI
into one point

A conversation, then we choose one decision point, then a pilot on your own texts, lasting [DURATION].

[email protected]