From Day 1, we designed Verkada with network security in mind. Our aim is to enable the latest security standards without the need for special technical configuration or maintenance. Here's an overview of the ways we accomplish this.

Data encryption at rest (Locally on Camera)

Video data is encrypted at rest use modern RSA and AES encryption standards. PKI encryption ensures that, even in the unlikely event that someone gets their hands on your Verkada camera, they'll find it impossible to extract any video data from its onboard storage.

Data encryption in transit 

By default, all Verkada systems encrypt data in transit using HTTPS/SSL. All communication is over Port 443. And Verkada cameras make only outbound connections to Verkada's cloud services.

Data at Rest (AWS)

Archived videos, user history, and audit logs are securely stored in AWS using AES 256-bit encryption

No port-forwarding

Unlike traditional CCTV systems, which often rely on port-forwarding of NVRs/DVRs to enable remote access, Verkada systems have no open ports. Remote access is enabled automatically via secure outbound connections over Port 443, so there's no need to configure a VPN. 

Single sign-on & 2-FA

Verkada support SAML/Oath for single sign-on and 2-factor authentication (via SMS and authenticator applications). Read more about user identify management.

Audit logs

Command logs user session details that can be audited. If your use case requires audit logs, let your Verkada account manager know.

Did this answer your question?