What security cameras can and cannot do

1. What cameras can do

A properly designed system can help an HOA in five practical ways.

1. Document activity in a covered area

A camera can show:

• When someone entered an area
• Which direction they traveled
• What vehicle was present
• What happened within the frame
• How long the activity lasted

This can help establish a timeline after an incident.

2. Preserve information people did not notice

Footage may capture:

• Clothing
• A vehicle
• A plate
• An access route
• Damage occurring

The information is useful only when the camera has the required view, detail, lighting, and recording settings.

DHS guidance emphasizes that camera selection, field of view, image detail, lighting, frame rate, storage, and system design all affect the result.

3. Support an investigation or insurance claim

Footage may help management, an insurer, or law enforcement understand what happened.

Its value can include:

• Confirming an approximate time
• Identifying a vehicle or person for further review
• Showing how property was damaged
• Resolving conflicting accounts
• Preserving evidence

Research reviewed by NIJ has found that video can aid post-event investigations, although the results depend heavily on how cameras are positioned, monitored, and integrated into the response process.

4. Support live awareness when someone is watching

Live video or alerts may help an authorized person notice:

• A gate problem
• Unauthorized activity
• A person needing assistance
• A developing safety issue
• A camera or system failure

A camera does not create a response by itself. Someone still needs to receive the information and know what to do.

5. Discourage some visible activity

A visible camera or sign may influence behavior in some locations.

The effect is not guaranteed and can vary by incident type, location, camera coverage, and whether people believe the system is operating.

Studies of public CCTV have produced mixed results, including differences across property crime, vehicle crime, violent crime, and different deployment settings.

The board should describe deterrence as a possible benefit rather than a promise.

2. What cameras cannot do

The limitations matter as much as the features.

1. See beyond the covered area

A camera cannot show:

• Activity behind it
• An uncovered entrance
• Events blocked by vehicles or landscaping
• What happened before recording began
• What occurred after someone left the frame

More cameras can reduce gaps, but every system still has boundaries.

2. Guarantee identification

A recording may show a person or vehicle without providing enough detail to identify them.

Image quality can be affected by:

• Distance
• Angle
• Lighting
• Motion
• Obstruction

The camera may document the incident without answering who was responsible.

3. Prove intent or responsibility

A person or vehicle appearing near an incident does not prove involvement.

Footage may show:

• Presence
• Movement
• Timing
• Visible actions
• Physical characteristics

It may not show why the person was there, what happened outside the frame, or whether someone else was involved.

4. Prevent every incident

A camera generally records or transmits information.

It does not physically:

• Lock a gate
• Improve lighting
• Stop a vehicle
• Repair an access weakness
• Respond to an emergency

Cameras work best as one part of a broader plan involving physical conditions, procedures, people, and response.

5. Manage themselves

The HOA still needs someone to:

• Check system health
• Manage users
• Review valid requests
• Preserve relevant records
• Audit access and sharing

An unattended system can fail quietly or collect footage that no one can retrieve when it matters.

3. What makes footage useful

A useful camera should have one clearly defined purpose.

Examples include:

• Capture vehicles entering one lane
• Record activity at the package-room entrance
• Show who uses a pedestrian gate
• Cover a vandalism-prone wall
• Document activity near a clubhouse door

Avoid assigning a camera a vague purpose such as “cover the parking lot.”

Five design questions

1. What exact event should this camera help us understand?
2. Where must the subject appear in the frame?
3. What detail must be visible?
4. What lighting and movement conditions will exist?
5. How quickly will the footage need to be found?

These questions should guide placement, camera type, retention, and testing.

Test under real conditions

Test the system:

• During the day
• At night
• With normal vehicle or walking speeds
• In common weather and lighting conditions
• From the actual search and export interface

Do not evaluate the system only through a vendor demonstration or live image on installation day.

4. What cameras still require from the HOA

Technology does not replace governance.

Before activation, the HOA should define five things:

1. Purpose. The incidents and areas the system is intended to address.
2. Access. The small number of people permitted to use it.
3. Retention. How long routine records are kept.
4. Sharing. When information may be provided to residents, insurers, attorneys, or police.
5. Response. What happens after a report, alert, or system failure.

Connected cameras should also be treated as networked devices that require account security, updates, access controls, and vendor support. NIST guidance recommends evaluating how connected devices manage identification, configuration, data protection, software updates, and cybersecurity status.

5. How to evaluate whether cameras are helping

Do not measure success only by whether incidents increased or decreased.

Many factors can affect incident totals.

Use five practical measures:

1. Availability. Was the camera working when needed?
2. Coverage. Did it capture the location and activity it was intended to cover?
3. Usefulness. Did the footage provide relevant information?
4. Workload. How much staff or manager time did searches and requests require?
5. Cost and trust. Were the expense, resident concerns, and operating responsibilities acceptable?

A camera that produces clear, relevant footage for its defined purpose may be useful even when it does not directly identify a person.

A camera that is frequently offline or pointed at the wrong area is not successful simply because it was installed.

A realistic camera statement

The board should be able to describe the system this way:

The cameras are intended to provide useful information after defined incidents in selected common areas. They may also discourage some visible activity. They do not guarantee prevention, identification, or complete coverage of the property.

This sets a fair expectation for directors and residents.

Camera-expectations checklist

Before approving or renewing a system, confirm that:

• Every camera has one defined job.
• The proposed view has been tested under real conditions.
• The board understands what remains uncovered.
• Someone is responsible for operating and reviewing the system.
• Success will be measured using practical results rather than promises.

Sources and further reading

• Government technical resource

  Department of Homeland Security, Video Security Systems Technology Handbook

• Government research resource

  National Institute of Justice, CCTV and Crime Prevention

• Government research resource

  National Institute of Justice, CCTV Impacts on Crime and Case Clearances

• Government research resource

  National Institute of Justice, Video Analytics and Event Response

• Government cybersecurity resource

  NIST, IoT Device Cybersecurity Guidance

• Government planning resource

  CISA Security Planning Workbook

FAQ