SIRA CCTV requirements are usually encountered at the point of installation, which is later than ideal. The Security Industry Regulatory Agency regulates security work in Dubai, and its expectations shape camera selection, coverage, recording, storage and the paperwork that must survive handover. Understanding them early keeps a design approvable and avoids rework.
What SIRA regulates, and what it does not
SIRA is the Dubai authority responsible for regulating the security industry, including the companies that supply, install and maintain security systems. Its remit covers the licensing of security businesses and the approval of security system designs and installations. It is not a building-permit authority and it does not replace Civil Defence or municipality approvals. A Dubai project often needs all three, and each reviews a different aspect of the same installation. Assuming one approval covers another is a common cause of delay at handover.
For CCTV specifically, the practical effect is that a system intended for a Dubai property should be designed against SIRA's published technical requirements from the outset. Those requirements address how cameras are selected and installed, what the system records, how long recordings are kept, and who may access them. Design decisions taken without reference to them tend to surface as comments on a submission rather than as problems the contractor can resolve on site.
CCTV design approval: what the submission actually covers
A design submission is not a single drawing. It is an argument that the proposed system meets the applicable requirements, supported by equipment data, coverage information and system architecture. Reviewers look for consistency: the cameras on the layout should match the schedule, the schedule should match the submittals, and the recorder capacity should be demonstrably adequate for the number of cameras and the retention period claimed.
- Site and floor layouts showing camera positions, coverage intent and blind spots
- Camera schedule with resolution, lens, low-light specification and mounting height
- Recording architecture: recorders, storage, network and redundancy arrangements
- Retention period, recording schedule and frame-rate assumptions
- Access arrangements, user roles and control-room provisions
- Business licensing and engineer credentials where the authority requires them
Requirements are revised from time to time. Confirm the current submission format, technical criteria and fee schedule directly with SIRA before a design is finalised. Guidance inherited from an older project is not a reliable basis.
Coverage, camera selection and storage expectations
Coverage is assessed against purpose. An entrance camera needs to identify a person or a vehicle plate under the lighting that actually exists at that door, not under studio conditions. A perimeter camera needs to detect approach along a fence line. Treating every position as an identification point inflates cost and rarely improves the system, while treating an identification point as detection leaves the operator unable to act on what is recorded.
Storage expectations follow from coverage. Resolution, frame rate, codec and retention period together determine the recording load, and the recorder must be sized with headroom rather than exactly at the calculated figure. Where a site changes camera count or retention after approval, the storage basis should be recalculated and, if the change is material, reflected in an updated submission. A recorder that silently overwrites recordings early is a compliance problem, not only a technical one.
Existing systems and ongoing compliance
An installed system is not automatically compliant because it was once approved. A change of tenant, camera replacements, recorder upgrades, network segmentation and additions to coverage can each move a system away from its approved basis. When taking over a property, ask for the approval record, the as-built drawings and the equipment schedule, then compare them against what is physically installed. The gap you find is the scope of the rectification work.
Ongoing compliance also has a maintenance dimension. Lenses go out of focus, cameras are re-aimed, storage fails, and clock drift makes recordings useless as evidence. A maintenance regime that includes periodic image-quality checks, storage verification and time synchronisation keeps a compliant system compliant. Records of those checks are worth keeping, because they demonstrate that the operator has been exercising reasonable care over the installation.
Documentation that should survive handover
Handover documentation is usually the weakest part of a security project and the most useful part six months later. The pack should include as-built drawings, camera and equipment schedules, configuration backups, IP addressing, user accounts and permissions, the storage sizing calculation, warranty and support information, and the approval correspondence itself. Digital copies should be stored where the facilities team can reach them, not only in the installer's project folder.
For owners and consultants, the practical conclusion is to treat SIRA requirements as a design input rather than a closing formality. Clarifying coverage, retention and recorder capacity at design stage costs a meeting; discovering the mismatch after installation costs equipment, rework and a delay to occupancy. Most compliance risk is genuinely cheaper to remove before the purchase order is issued.
Discuss a similar requirement