Person confirmed
Each individual is checked against your authorised list and bound to the role they were granted before access opens.
Reference · DK-03
Control · Person and machine confirmed
Scope · Company-owned equipment only
Record · Kept for every enrolment
Identity and device verification before a single connection is opened
Access is only as strong as the certainty behind it. Before anyone reaches your internal systems, we confirm who the person is and that the machine in their hands belongs to the organisation. Both checks happen on our side, and every one is recorded.
We provide services exclusively to businesses and organizations. We do not offer consumer or personal-device support. Minimum engagement: organizations with 10 or more staff who need access.
Two questions, answered before access
The first question is who. We confirm that the person requesting access is the person your organisation has authorised, using the staff records and approvals you provide, and a verification step that ties the individual to that authorisation. A name on a list is a starting point, not a confirmation, so we go a step further and bind the person to the role they were given.
The second question is which machine. Access is granted to equipment the organisation owns and has chosen to include in the arrangement. A privately owned computer is never enrolled, and this is not negotiable. A machine that is not ours, not yours and not on the approved list simply does not join. That single rule removes a great deal of risk before anything else is done.
How we verify a person
- We match the request against the current list of authorised staff and the role they hold.
- We confirm the identity of the individual through a step that proves they are who the record says they are.
- We confirm that the manager or owner responsible for that role has approved the access.
- We record the result, the date and the person who approved it.
How we enrol a company machine
Enrolment is something we do, not something your staff are asked to do. We prepare the machine during onboarding so that when the person sits down, the access is already in place. They do not obtain anything, run anything or load anything of their own. The preparation happens before the machine reaches the desk, or on a day arranged around your working week.
Each enrolled machine carries a record of what it is, who it was issued to and when it joined the arrangement. When a machine is replaced, retired or reassigned, the record follows, so the list of enrolled equipment never becomes a mystery. An organisation that knows exactly which machines may reach its systems is in a far stronger position than one that merely hopes.
Machine enrolled
Only company-owned equipment joins the arrangement. Personal machines are never included, whatever the request.
Approval captured
We hold the approving manager or owner alongside each enrolment, so the trail answers the question of who allowed it.
Records updated
Replacements, retirements and reassignments are reflected in the record as they happen, keeping the picture current.
What happens when something does not match
Occasionally a request and a record disagree. A machine is not on the approved list, an authorisation is out of date, or a person is not yet confirmed. When that happens we stop and go back to your point of contact rather than pressing on. Verification is not a formality to be waved through; it is the point at which weak access is caught. We would rather delay one enrolment by a day than open a connection that should not exist.
Why this protects the organisation
Most access failures do not come from clever outsiders. They come from access that was granted once and never reviewed, equipment nobody remembers issuing, or people who left and kept their reach. Verifying both the person and the machine, and recording both, closes those gaps before they open. Combined with the policy and review work that sits alongside it, this is what keeps an arrangement trustworthy over years rather than weeks.