Anyone who manages property, whether a hangar complex, an airfield-adjacent estate or a portfolio of leased buildings, ends up holding sensitive information: tenant files, access codes, lease terms, payment records. Protecting it needs a watch that runs steadily, and the discipline behind that watch is SOC Ops. This starter glossary explains the terms in a way that property and aviation-business readers can follow, with evidence drawn from public reference material and a few comparisons to estate management.
Why the vocabulary matters
When a security provider or an IT contractor presents a proposal, the words they use can sound interchangeable and still mean different things. A short shared dictionary lets you ask better questions and compare offers fairly. The reference we lean on is the xOps School Atlas page on SOC Ops, which also admits that the label itself is informal and that standards bodies often use other names for the same function.
The glossary
SOC (security operations centre)
The team and tools that watch an organisation’s systems for signs of trouble. In a small firm it may be one part-time person plus a provider; in a large one it is a staffed room. Europe’s cyber agency, as the Atlas recounts, observes that in small organisations the two labels frequently describe one and the same group.
Alert
A notice that something may be wrong. Think of a door sensor on a vacant unit: it tells you the door opened, not whether it was the cleaner or an intruder.
Triage
The first quick assessment, comparable to a property manager walking past a reported leak to decide whether it is a drip or a flood.
Disposition
What was finally decided about an alert, written down. The Atlas names four: true positive (a real problem), benign positive (a correct detection of allowed activity), false positive (nothing behind it) and undetermined (not enough information).
Benign positive
Worth its own entry because it is so common. If a contractor with an approved key enters a building at night, the sensor is right and the event is still acceptable. The fix is context, such as a contractor schedule, not a quieter sensor.
SIEM
The platform that gathers event records from many systems and raises alerts. Examples in the reference include Microsoft Sentinel and an open-source option called Wazuh.
SOAR
Software that automates steps of a response. Official guidance the Atlas relays says it tends to be a poor match for young, unsettled setups, so get the by-hand routine steady beforehand.
Playbook
A written procedure for a known situation. If a type of event occurs monthly or more, the Atlas expects an approved procedure on file, much like a standard operating routine for a burst pipe.
Handover
The structured passing of open items from one shift to the next, recorded in a pass-down log that both sides sign.
MSSP and MDR
Outside firms that monitor on your behalf. The Atlas stresses, citing MITRE, that you cannot outsource accountability: property owners and executives remain answerable.
Median and percentile
Ways of summarising waiting times. A median is the middle value; a ninetieth percentile shows how slow the slowest tenth is. They are fairer than a plain average, which a single outlier can distort.
Evidence you can use in conversations
A worked month in the Atlas gives numbers worth remembering. Of 4,200 alerts, about 4.2 percent were genuine, and routine non-issues absorbed roughly 72 percent of the triage hours. Cutting one thousand harmless alerts would free roughly 117 hours a month. In property terms, that resembles a maintenance desk spending most of its week on tickets that never needed a visit. When you ask a provider about their approach, ask how they classify alerts and what share ends as legitimate activity, because their answer reveals how much context they build in.
The same reference reports a lab where the overall typical wait was seven minutes while the overnight typical wait was over eight hours. Ask any provider to show their night-time figures separately.
Why this belongs in a property conversation
Real estate decisions already rely on layered review, careful documentation and clear accountability. Our overview of simplifying complicated property choices argues for breaking decisions into manageable steps, and the same approach suits security: one queue, defined verdicts, a recorded reason for each closure. Likewise, the explanation of the overall approach to real estate used by this firm shows the value of a consistent process, which is exactly what a steady SOC Ops routine is for.
Common misunderstandings
- A security operations centre is not a network operations centre. One watches for hostile behaviour; the other watches availability.
- The acronym SOC has nothing to do with SOC 2, an auditor-issued assurance document.
- Buying a tool does not equal having a functioning watch. The Atlas gives a government-report example in which a department paid for extra logging, and the review concluded that the purchase alone would not have been enough.
A tiny scenario to make the terms stick
Suppose a leasing office notices a login to its tenant portal from a city the manager has never visited. That is an alert. The first person to look performs triage and checks whether the account holder travels. The answer, perhaps, is that the leasing agent was at a trade show, so the verdict is benign positive, and a note goes on the approved-travel list. Had the account belonged to someone on leave, the verdict would flip to a real problem and the item would go up a tier with the context attached. At the end of the day, the pass-down note records what happened. Every glossary term above appears in that one small story.
Questions to ask a provider
- How are alerts closed, and are reasons recorded?
- Do you report median and slow-tail waits per shift?
- Who may take automatic containment actions, and on which assets?
- How do handovers work between shifts?
- What happens at night and on holidays?
This glossary is general information, not professional advice. Use it as a starting point, then adapt the terms to your own estate and ask qualified people about your specific obligations.

