Under attack? Emergency incident response, remote or on-site.Get help now →Call (360) 524-3477

Penetration testing · Olympia, Tacoma & Seattle

Penetration testing that shows how far an attacker could get.

A scan lists possible problems. A penetration test proves which ones matter. With your written permission, we try to break in, then show you each step we took and how to shut it down.

Testing starts only after the scope and rules of engagement are signed.

When businesses book a pen test

A pen test usually starts with someone else asking a question: an insurer, a large customer, an auditor or a contracting officer. Others follow a big change, like a new firewall, a move to the cloud or a customer portal going live.

Tests are led by Brandon Whitley, who spent 22 years in Air Force cyber operations. He tests by hand, using the techniques attackers use, and writes the report himself.

Common reasons to test

  • Cyber insurance: an application or renewal asks when you were last tested.
  • Customer security reviews: a larger client wants a recent third-party report.
  • PCI DSS: if card data touches your own systems, Requirement 11.4 calls for internal and external tests at least every 12 months and after significant changes.
  • Contracts: government and defense work that asks for proof your systems have been tested.
  • After a change: a new firewall, a cloud move, an office move or an app launch.
  • After an incident: to confirm the way in is closed for good.

Test types

Pick what to test.

Most small businesses start with an external test and add the others as their needs grow.

External network

Anything an outsider can reach: remote access, VPNs, firewalls, email and web servers, and the old test system nobody turned off. We find what’s exposed, then try to get past it.

Internal network

Starting from one office computer or network jack, how far could someone get? File shares, admin accounts, backups and the systems that control everything else.

Web applications

Logins, password resets, customer portals, payment and upload forms. We check whether one user can reach another’s data and whether accounts can be taken over, including the flaws on the OWASP Top 10.

Wireless

Whether your Wi-Fi password holds up to cracking, whether guest Wi-Fi is walled off from office systems, and whether a fake access point would get noticed.

Findings you can check for yourself

A finding without proof is only an opinion. Each one in our report shows where we started, what we did, what it got us and the exact change that would have stopped us, with screenshots and commands so your IT team can reproduce it.

The report opens with the story of the test in order, so an owner can follow how a small slip turned into real access. It ends with a fix list ranked by risk.

Sample finding (illustrative)

  • Severity: High
  • Issue: the same local administrator password is set on all office PCs.
  • What it allowed: from one PC, sign-in to the others and to the file server.
  • Evidence: timestamped screenshots and the commands used.
  • Fix: turn on Windows LAPS so each PC gets its own rotating password.
  • Retest: confirmed closed after the change.

This example is made up to show the format. It isn’t from a client report.

The process

From first call to retest

  1. 1

    Agree the target

    We start with who’s asking for the test and why, then pick the systems, addresses and apps that answer that question.

  2. 2

    Map what’s exposed

    Reconnaissance comes first: what’s reachable, what’s running on it and which versions. This is where forgotten systems turn up.

  3. 3

    Try to get in

    Hands-on attempts to exploit what we found, chaining small weaknesses together and stopping short of anything that could harm your data.

  4. 4

    Report and retest

    A readout call walks through the findings. Once fixes are in, we retest and update the report to show what’s closed.

Careful with your systems

A penetration test should never become the outage. Before anything starts, you approve the scope, the dates and who we call if something looks wrong.

Checks that could slow systems down are scheduled after hours or left out, and you can pause testing at any point with one phone call.

Ground rules we test by

  • Written authorization and scope, signed before testing
  • Testing windows you choose, including after hours
  • No denial-of-service or destructive tests unless you ask for them in writing
  • A named contact on your side while testing runs
  • If we find a critical hole, or signs someone else is already inside, we call you that day
  • We take only what we need to prove a finding, and keep it confidential

Questions

Before you book a test

How much does a penetration test cost?

It depends on the scope: how many internet-facing systems you have, the size of the internal network, and how many web apps and user roles need testing. After a short scoping call you get a fixed quote, so the price doesn’t change once testing starts.

How long does testing take?

Smaller external tests often finish within a few days. Internal and web application tests usually take longer, depending on size. The timeline comes with your quote, and the report follows the testing.

Will the report satisfy our insurer or customer?

Reports include an executive summary, the scope and dates, how we tested, and each finding with its severity, evidence and fix. Tell us who’s asking up front and we’ll make sure the report covers what they need to see.

Can you test Microsoft 365 or Google Workspace?

Yes, within the testing rules Microsoft and Google publish. We look at sign-in protection, admin roles, sharing settings and the mailbox rules attackers like to set up after a successful phish.

What do you need from us before testing?

A signed authorization from someone who can approve it, the list of what’s in scope (internet addresses, web app links, office locations), a contact during testing and, for web apps, a test account for each type of user.

Do you test remotely or on-site?

External and web application tests run remotely. Internal network and Wi-Fi tests happen at your office, with on-site work around Olympia, Tacoma and Seattle.

Related services

Before and after the test

Cybersecurity audits

A broader review of settings, accounts, backups and policies that pairs well with a test.

Security audits →

Managed IT services

We can close the findings for you and keep new ones from piling up.

Managed IT →

Emergency incident response

If testing uncovers signs of an earlier break-in, we can move straight into response.

Incident response →

App & software development

Building a portal or app? Have it tested before customers log in.

App development →

Someone asking for a pen test report?

Tell us who’s asking, what you run and your deadline. We’ll reply within one business day with a scope and a quote.