Industry
What 33 CFR Part 105 Requires of Cameras at an MTSA-Regulated Waterfront Facility
33 CFR 105.275 is titled "Security measures for monitoring." Most operations managers at MTSA-regulated facilities have read it, in the sense that it appears in the Facility Security Plan sitting in a binder. Very few have read it as an engineering specification, which is what it is.
Read that way, Part 105 stops being paperwork. It states capability requirements, and a facility can satisfy them on paper with equipment that will not hold up through a grid loss or a MARSEC escalation. This piece walks through what the monitoring and maintenance sections actually require, and where the gap between the plan and the hardware usually opens.
Who This Applies To
MTSA-regulated waterfront facilities operating under an approved Facility Security Plan. If your facility has an FSP, a Facility Security Officer, and a Captain of the Port who reviews it, Part 105 Subpart B is your requirement set.
What follows is a summary of federal regulation, not a compliance determination. Your approved FSP and your local Captain of the Port govern your specific facility, and where the two differ from a general reading, they win.
105.275 Read as an Engineering Requirement
The section requires that "the facility owner or operator must ensure the implementation of security measures in this section and have the capability to continuously monitor, through a combination of lighting, security guards, waterborne patrols, automatic intrusion-detection devices, or surveillance equipment, as specified in the approved Facility Security Plan (FSP)" (law.cornell.edu/cfr/text/33/105.275, retrieved 2026-08-13).
Read the list, because it matters to how you spend money. Surveillance equipment is one of five named means, and the approved FSP decides which combination applies at your facility. Cameras are not the mandated answer. What the regulation fixes is the capability. Everything below is about whether that capability actually exists, whichever means your FSP specifies.
Three phrases in that section do the real work.
Continuously. Not during staffed hours. Not when the weather cooperates. Paragraph (b)(2) requires monitoring capability "able to function continually, including consideration of the possible effects of weather conditions or of a power disruption" (law.cornell.edu/cfr/text/33/105.275, retrieved 2026-08-13). Read that precisely: the regulation requires the capability to function continually, and it requires that you have considered weather and power. It does not itself set a survival standard for either. Iron Gate Technologies' position is that a facility which has considered a power disruption and still goes dark when the grid does has not closed the gap, so we recommend backup power on the monitoring chain and low-light performance verified on site. That is our engineering recommendation rather than a demand the regulation makes.
At all times, including the period from sunset to sunrise and periods of limited visibility. This is the phrase that quietly rules out a great deal of installed equipment. Cameras that produce a usable image at noon and a grey rectangle at 3 a.m. do not satisfy a requirement written specifically to cover darkness. Neither does a system that goes effectively blind in fog or driving rain, which on a waterfront is not an edge case but a season.
The facility area, including shore and waterside access to it. Coverage extends to the approaches, not just the fence line and the gate. On a waterfront facility the approach is water, and a camera plan drawn around vehicle entrances has left the actual approach uncovered.
Put together, those three phrases describe a system that has to see in the dark, watch the water, and account for a power disruption. Any one of them can be missed by a system that looks complete on a site plan.
The Escalation Ladder Is a Capacity Question
MARSEC levels are where the engineering consequence gets sharp, because each level adds measures on top of the last.
At Level 2, the FSP specifies "additional security measures, as specified for MARSEC Level 2 in the approved FSP," which may include increasing the coverage of surveillance equipment, increasing the frequency of foot, vehicle, and waterborne patrols, assigning additional personnel to monitor, and increasing lighting intensity.
At Level 3, the measures may include "Switching on all lighting within, or illuminating the vicinity of, the facility," "Switching on all surveillance equipment capable of recording activities within or adjacent to the facility," and "Maximizing the length of time such surveillance equipment can continue to record" (law.cornell.edu/cfr/text/33/105.275, retrieved 2026-08-13).
| MARSEC level | What the regulation contemplates | The infrastructure question it raises |
|---|---|---|
| Level 1 | Continuous monitoring capability covering the facility area including shore and waterside access, at all times including sunset to sunrise and periods of limited visibility, able to function continually including consideration of the possible effects of weather conditions or of a power disruption | Low-light performance, waterside coverage, and runtime independent of the grid |
| Level 2 | Additional measures per the approved FSP, which may include increased surveillance coverage, more frequent foot, vehicle and waterborne patrols, additional monitoring personnel, and increased lighting intensity | Whether added coverage means equipment already installed, or a procurement cycle you do not have time for |
| Level 3 | Measures which may include switching on all lighting, activating all surveillance equipment capable of recording, and maximizing the duration of that recording | Power budget with every device energized, and retention headroom that exists before the escalation rather than after |
The right-hand column is the point. Level 3 does not arrive with a lead time. When the Coast Guard raises MARSEC, the capacity to comply either already exists in your building or it does not.
Two failures follow directly from that.
The first is power. Level 3 contemplates all lighting on and all recording equipment active, which is the highest-draw state your facility will ever be in, and elevated MARSEC frequently coincides with the conditions that put the grid at risk. A backup design sized for normal load has not been sized for the state the regulation actually asks about. We have written separately about what keeps a camera system recording when the grid goes down, and the arithmetic there applies with more force here.
The second is retention. "Maximizing the length of time such surveillance equipment can continue to record" is a storage sentence. A facility whose array is sized precisely to its Level 1 retention policy has no headroom on the day it is told to record more, for longer, from more devices. Storage sizing is arithmetic and can be run in advance, which means running out of it during an escalation is a planning failure rather than a surprise.
105.250 Turns Maintenance Into a Compliance Artifact
The section that gets least attention has the sharpest teeth. 33 CFR 105.250, "Security systems and equipment maintenance," reads in full:
"(a) Security systems and equipment must be in good working order and inspected, tested, calibrated, and maintained according to manufacturers' recommendations.
(b) Security systems must be regularly tested in accordance with the manufacturers' recommendations; noted deficiencies corrected promptly; and the results recorded as required in 105.225 of this subpart.
(c) The FSP must include procedures for identifying and responding to security system and equipment failures or malfunctions."
(law.cornell.edu/cfr/text/33/105.250, retrieved 2026-08-13)
Three obligations sit in those sentences, and each one changes how a camera system should be specified and supported.
Testing has to happen and has to be recorded. Not "the cameras looked fine when I walked past." Regular testing per the manufacturer's recommendations, with results recorded. That presumes a system that can be tested and a manufacturer who publishes recommendations to test against.
Deficiencies must be corrected promptly. A camera down at an MTSA facility is a documented deficiency with a correction obligation attached to it. This is where hardware support terms become a compliance variable rather than a service preference. If a failed unit takes three weeks to replace, you own a documented, uncorrected deficiency for three weeks. We have argued elsewhere that the recovery window matters more than the failure rate, and at a regulated facility that stops being an operational argument and becomes a paperwork one.
The FSP must cover failure procedures. Identifying and responding to equipment failure is a plan requirement. A system that fails silently, with no health monitoring and no alerting, makes the identifying half impossible to perform.
Where These Systems Actually Fail
Four patterns account for most of the gap between an approved plan and a system that holds up.
Coverage stops at the fence. The camera plan was drawn around vehicle gates and the perimeter, and the waterside approach the regulation names is covered by one wide shot that resolves nothing.
Everything depends on the grid. Continuous capability is asserted in the plan and delivered by equipment that stops when utility power does, with a UPS sized for an orderly shutdown rather than for continued operation.
No test records exist. The equipment may well be in good working order. Nobody can demonstrate it, which is a 105.250(b) problem regardless of the hardware's actual condition.
Retention is sized to the floor. The array holds exactly the policy minimum, so Level 3's instruction to maximize recording duration has nowhere to go.
Designing So Escalation Is a Switch
The design goal is that raising MARSEC changes a setting rather than starting a project.
That means low-light and adverse-weather performance specified at Level 1, because the regulation asks for it at Level 1. It means runtime independent of the grid, sized against the all-devices-energized state rather than normal draw. It means waterside and approach coverage in the original camera plan. It means retention headroom above the policy minimum, with the extra capacity already installed. And it means health monitoring that surfaces a failure the day it happens, so the prompt correction clock starts when the failure does rather than when somebody notices.
Iron Gate's Position
We build for continuous operation independent of the grid, with on-premise recording under facility control, which is the architecture the continuity language in Part 105 points toward. For waterfront work specifically, our experience is in marina and waterfront deployments where salt, weather, and waterside approaches are the design problem rather than an afterthought.
We do not certify FSP compliance and we cannot. The FSP is approved by the Captain of the Port, and no vendor can hand you a compliance determination. What we can do is design the system so that the capability the regulation describes is actually present in the hardware, and so that the test and maintenance records 105.250 requires are something your team can produce without inventing a process from scratch.
On power, we would rather remove the dependency than back it up. A generator or a battery bank carries you through a grid loss, so the answer lasts as long as the fuel or the charge. Solar with storage answers the same clause by not being on the grid at all. Both are legitimate choices, and we are not telling you which to buy. We are saying a runtime figure and an independence figure are different promises, and the clause above is about a capability that has to keep working.
The harder case is a MARSEC escalation. A change in level can call for coverage on ground that had none the week before, on a timeline set by the Captain of the Port rather than by your capital cycle. Running power and conduit to a pier head, a far fence line, or a temporary staging area is not a project that fits inside that window. Portable solar units do fit inside it, because the install is a placement rather than a build. That is the specific reason we make them.
Say the obvious thing plainly: none of this is required, none of it satisfies 105.275, and no equipment makes a facility compliant. The regulation fixes a capability and your approved FSP decides the means, which may not include surveillance equipment at all. This is our recommendation, in our own register, and you should read it as exactly that.
Common Questions
What does 33 CFR Part 105 require for security cameras?
Section 105.275 requires the capability to continuously monitor the facility area including shore and waterside access, at all times including sunset to sunrise and periods of limited visibility, through a combination of lighting, security guards, waterborne patrols, automatic intrusion-detection devices, or surveillance equipment as specified in the approved Facility Security Plan. That monitoring capability must be able to function continually, including consideration of the possible effects of weather conditions or of a power disruption. Section 105.250 requires testing, maintenance, prompt correction of deficiencies, and recorded results.
What are MARSEC levels and what changes at each one?
MARSEC levels are the maritime security levels that scale required measures with threat. Level 1 is the baseline continuous monitoring requirement. Level 2 adds measures specified in the approved FSP, which may include expanded surveillance coverage and increased patrols and lighting. Level 3 may include all lighting on, all recording equipment active, and recording duration maximized.
Does the Coast Guard require video recording at an MTSA facility?
Part 105 states monitoring capability requirements rather than mandating a specific technology, and the approved FSP specifies how a given facility meets them. The Level 3 language about surveillance equipment capable of recording, and about maximizing that recording duration, presumes recording capability is present.
How often must security cameras be tested at a port facility?
Section 105.250 ties testing frequency to the manufacturer's recommendations rather than naming an interval, and requires that results be recorded as required in 105.225. That makes the manufacturer's published maintenance guidance a compliance input.
What is required in a Facility Security Plan for surveillance equipment?
Among other things, 105.250(c) requires that the FSP include procedures for identifying and responding to security system and equipment failures or malfunctions. Monitoring measures for each MARSEC level are specified in the approved FSP under 105.275.
Does a camera outage put us out of compliance?
A camera not in good working order is a deficiency under 105.250, which carries an obligation to correct it promptly and to record the result. How that is assessed at your facility is a matter for your FSP and your Captain of the Port. The practical implication is that hardware replacement speed is a compliance variable.
Sources
- 33 CFR 105.275, Security measures for monitoring, law.cornell.edu/cfr/text/33/105.275, retrieved 2026-08-13
- 33 CFR 105.250, Security systems and equipment maintenance, law.cornell.edu/cfr/text/33/105.250, retrieved 2026-08-13
- 33 CFR Part 105, Subpart B, Facility Security Requirements
Ready to Talk Security?
Our engineering team can walk you through the right solution for your environment.
Book a Security Assessment