Small Modular Reactor Security
SMRs compress the footprint, the schedule, and the build model. That compression means the window for designing security in, rather than bolting it on afterward, is shorter and earlier than most utilities are used to.
Security-by-design only works if 'early' means early enough
A smaller reactor footprint is not just a smaller version of the same security problem. Vital areas sit closer together. Fewer structures carry more of the protective function. Standoff distances that were generous on a large-site layout can disappear entirely on a compact one. Getting the protective strategy right on an SMR means treating Design Basis Threat considerations and vital area identification as inputs to the site and reactor layout, not as a review performed after the layout is already fixed.
The modular, factory-build model changes the calendar further. Decisions that would normally happen on the construction site — where a barrier sits, how cabling and conduit are routed, where an access point lands relative to a vital area — are increasingly made at the module level, in a factory, months before anything ships. Once fabrication of a module locks in, the cost and schedule impact of a late security finding is no longer a field change order; it can mean requalifying a manufacturing process. Security has to be at the engineering table before that lock-in happens, not after.
Multi-unit and co-located SMR deployments add a layer most single large-unit programs never have to resolve: shared versus dedicated protected areas, shared versus dedicated response complement, and target set analysis that has to account for one unit's status affecting the required posture at the unit next to it. Those questions are answerable, but only if they are asked during design.