Skip to content

What we protect

Offices.

The front door, and the room behind it.

Most testing points at the network and the applications. We also go through the front door: whether somebody can walk in, what they can reach once they are inside, and what the guest network hands out to anyone who never gets past reception.

Where this gets in

the front door, and the room behind it.

An office is full of things nobody thinks of as computers: cameras, door controllers, printers, meeting-room screens — and a constant flow of visitors.

  • We come in the way that gets skipped

    Most testing points at the network and the applications. We also go through the front door of your offices, because that route is the one nobody has tried.

  • Everything on one network

    Cameras, door controllers, printers, meeting-room screens, corporate laptops and visitors tend to share one network — and everyone agrees they shouldn’t.

  • The guest network is a legal question first

    Offering guest Wi-Fi means processing personal data. The usual setup has no recorded consent, no stated purpose, no retention position and no record of who connected.

The services

two services, and what each one covers.

Testing the building the way someone hostile would, and a guest network that stands up to a review.

/ 01

physical & on-site testing

We come in through the front door.

The office itself, tested rather than assumed: whether somebody can walk in, what a device inside the building can reach once it is connected, and what the wireless networks give away. The things nobody thinks of as computers are in scope too — door controllers, cameras, printers and meeting-room screens. Delivered to published methodology, including PTES and OWASP Wireless.

  • the front door, not only the perimeter firewall
  • what a device inside the building can actually reach
  • door controllers, cameras, printers and meeting-room screens in scope
  • the wireless networks tested to published methodology

/ 02

guest network & visitor access

Guest Wi-Fi that survives a data protection review.

A guest network where the compliance position comes first. Visitors see clear terms and must actively agree, then register with an email address; the notice states what is collected, why, how long it is kept and that it is not shared. Certificates renew themselves, so the portal never warns visitors that the connection is untrusted — and nobody at the front desk has to read a password aloud across the lobby.

  • consent that is explicit and recorded
  • a stated purpose and a defined retention period — 30 days on the site we built it for
  • each session attributable to a registered visitor
  • terms in more than one language where the site needs it

Where to start

where this work usually starts.

Where to start, and two engagements where this exact work has already been delivered.

engagement

security posture assessment

Find out where you actually stand: which gaps matter, which don’t, and a short list in the order things should be fixed.

view details
case study

Guest Wi-Fi that survives an audit

Consent explicit and recorded, purpose stated, retention defined at 30 days, every session attributable — every question a data protection review asks, answerable.

read the case study
case study

Segmentation nobody notices

A large site with cameras, door controllers, printers, meeting-room screens and constant visitor traffic, separated into twelve networks — and printing, scanning and screen sharing still worked.

read the case study

the other five things we protect.

People

The inbox, and the person reading it.

4 services

Devices

Laptops nobody manages.

2 services
See all 18 services in one list

Next step

test the front door.

Guest Wi-Fi is usually the cheapest compliance gap to close and one of the most commonly ignored, which often makes it the fastest visible result in a wider programme. The front door is the other half: the network can be built correctly and still be reachable by anyone who gets past reception.