Risk management
November 17, 2026
•
4 min read

Physical Penetration Testing in San Francisco: Set the Goal Before the Test

A physical penetration test with no stated goal produces a story. What to decide in San Francisco before you buy one: the question, the rules, and who knows.

Physical Penetration Testing in San Francisco: Set the Goal Before the Test

When a company asks for a physical penetration test, the first question is usually what the tester is allowed to do. The better first question is what the test is for. A test that has no stated goal produces a story. A test with a goal produces a decision. In San Francisco, where offices sit in towers, converted warehouses, and shared floors, the goal shapes everything else.

Pick the question before the method

Three questions come up most often. Can someone who does not belong get to the floor where we work? Can they reach a specific asset, such as a server closet, records room, or executive area? And do our people and procedures notice and respond? Each one calls for a different test, and a single engagement rarely answers all three well.

Rules of engagement are the real scope document

The written rules of engagement decide what the test can and cannot prove. They should name the buildings and floors in scope, the dates and hours, the techniques allowed and excluded, and who can stop the test. They should also say how the tester proves access without causing harm, for example by photographing a marker placed in a room rather than removing anything.

Each tester should carry a signed authorization letter and an emergency contact who knows the test is live. If a guard or police officer stops the tester, that letter and phone call should end the encounter quickly and safely.

Shared buildings need a landlord conversation

Many San Francisco tenants do not control their lobby, elevators, or stairwells. Testing those areas requires permission from the building owner or property manager, not only from the tenant. Skip that step and a test can become a trespass complaint. Our post on penetration testing in a San Francisco shared lobby covers that problem in more detail.

Who should know

Keep the circle small, but not empty. Someone with authority must know, and so must whoever can handle a real response if a guard escalates. If your own security staff are told the dates, you are measuring a rehearsal. If nobody senior knows, you are risking a real incident. Decide this deliberately and write it into the rules.

What the report should contain

A useful report lists what was attempted, what worked, what did not, and the evidence for each. It should rank findings by how much they matter and what each fix costs. Findings that need a procedure change belong in a separate list from findings that need hardware or staffing. A report with a dramatic summary and no fix list gives leadership a story and no budget decision.

What it is not

A penetration test is a sample of one attempt on one day. It shows that a path exists. It does not show every path, and a clean result does not mean none exist. Treat it as one measurement, and follow it with fixes and a retest.

Braav runs physical penetration testing, including in San Francisco. If you want help setting the goal and rules for a test before you buy one, book a call here.

Let’s Make Your Business Safer.

Need a quick consult or full security assessment? We’re here to help.