What’s actually in the file you just emailed to eleven people. Think about what a federated model of a finished building contains. Not the geometry. The intelligence.
It shows where the server room is, how thick its walls are, and which corridor leads to it. It shows every door, its hardware set, and which ones are card readers rather than keys. It shows camera positions, the security office, the generator, the UPS room, the fibre entry point, the fire alarm panel, and the exact route of every conduit connecting them. In a hospital it shows medical gas storage. In a retail development it shows the cash room. In a clinic it shows where records are held.
Now consider how many people have a copy. The design team, six subcontractors, an offshore drafting vendor, a bid list of twelve trades who did not win the work, a student who used a render in a portfolio, and whoever had access to the old FTP site that nobody has reviewed since 2021.
The construction industry has spent fifteen years getting better at sharing model data. It has spent almost none of that time deciding what should not be shared, or with whom.
The gap between how we treat drawings and how we treat models
A 2D drawing set is a slice of information. A model is a queryable database of the building. Those are not the same risk.
An attacker reading a drawing has to interpret it. An attacker with a model can filter it. Show me all doors with electronic hardware. Show me all equipment on the emergency panel. Export the room schedule and sort by department. Pull the asset register and read the make, model and firmware of every building automation controller in the facility. That is reconnaissance that would otherwise take weeks of physical surveillance, delivered as a file.
And the handover package is often worse than the model. O&M manuals routinely include controller IP addresses, network topology diagrams, vendor remote-access instructions, and default credentials that nobody ever changed. COBie deliverables list serial numbers and system identifiers. All of it sits in a project folder that dozens of people can still reach three years after substantial completion.
How this information actually escapes
It rarely escapes through a sophisticated breach. It leaks through ordinary practice.
The common data environment nobody prunes. Access is granted at mobilization and almost never revoked. Staff leave firms, trades finish their scope, and the permissions stay. Ask any project how many active CDE accounts belong to people no longer on the job, and watch the silence.
Tender distribution. Full drawing and model sets go to every bidder. Most lose. Nothing obliges them to destroy what they received, and few do.
Public procurement. Some institutional tenders publish complete documentation to a public portal, security systems included.
The convenience chain. A model too large for email becomes a WeTransfer link, then a personal Dropbox, then a USB drive in a laptop bag on the subway.
Offshore and freelance production. Perfectly legitimate, and often how shop drawings get produced economically, but the data lands on machines and in jurisdictions the owner never assessed.
Marketing. Renders, walkthroughs and case studies published with more detail than anyone reviewed.
Who cares about your model
Three groups, and only one is the stereotype.
Physical intruders. Theft, vandalism, and targeted access to a specific room. A model reduces the planning cost of all three.
Operational technology attackers. Building automation, access control and elevator systems increasingly sit on IP networks, and the asset data in a handover package is a shopping list. If the controller make and firmware version are documented, so are the published vulnerabilities.
Competitors and litigators. Detailed model data reveals pricing logic, fabrication methods and sequencing. It also becomes evidence, which matters more than most teams expect.
The standard almost nobody uses
There is already a framework for this. ISO 19650-5 covers the security-minded approach to information management, and it sits in the same family as the ISO 19650 parts most firms already reference for their BIM Execution Plans. Its core idea is simple. Before you decide how to share information, you assess whether the asset, or some part of it, is sensitive. If it is, you build a security strategy and a set of controls into the information management process rather than bolting them on afterward.
Most firms cite 19650-1 and 19650-2 in every BEP and have never opened Part 5.
What a reasonable firm can do this quarter
You don’t need a security program to make real progress. You need five decisions.
Run a sensitivity assessment at project start. Ask one question: is there anything about this building where disclosure creates physical, operational or privacy risk? Clinics, data rooms, courts, utilities, schools and anything with a cash or pharmacy function usually qualify. Most warehouses don’t. Write the answer down.
Separate the sensitive layer. Security devices, camera coverage, access control, and critical infrastructure routing can live in a restricted model or drawing set issued to a named list, not to the general distribution.
Classify and label the data. If your firm runs Microsoft 365, sensitivity labels can be applied to model and document sets so that restricted content cannot be forwarded outside the project domain. This is unglamorous and effective.
Put it in the contract and the BEP. Name who may hold the model, where it may be stored, what happens to it at completion, and what unsuccessful bidders must do with their copies. Extend the same terms to offshore vendors.
Scrub the handover. Before the O&M package is accepted, strip credentials, remove network diagrams from the general set, and confirm the asset register goes to the facilities team rather than the shared folder.
The uncomfortable question
Ask your project team where the model currently lives. Not the CDE. Everywhere. The personal drives, the vendor servers, the bidders’ archives, the laptop of the coordinator who left in March.
If nobody can answer, you have already published a map of the building. You just don’t know to whom.