How Habile iEYE protects your video
Video is sensitive because of who is in it. This page describes how the software is built to keep it to the people who should see it: separation between organisations in the database itself, short-lived signed access to every stream, and a record of every change and every viewing.
Last updated
- Nothing is sent to HabileLabsNo video, no camera list, no usage report. The appliance has nothing to check in with.
- Organisations separated by the databasePostgreSQL row-level security on every tenant table, not just in the application.
- Short-lived signed access to videoEach stream token allows one action on one camera, and expires.
- Every change and every viewing on recordWho changed what, and who watched which camera, for how long.
Four layers between a stranger and your footage
Separation between organisations
- Every tenant table carries a tenant id and a PostgreSQL row-level security policy
- The server runs as a database role that owns nothing and cannot bypass row-level security, and refuses to start if it could
- The tenant always comes from the signed-in session, never from the request
- Another organisation's resource answers "not found", never "forbidden"
Sign-in and sessions
- Passwords are hashed with scrypt; session tokens are random and stored hashed
- Two-step verification with an authenticator app (TOTP) and recovery codes, or an e-mailed code
- Single sign-on with OpenID Connect, SAML 2.0, LDAP or Kerberos
- Sign-in is rate-limited per account and per address, with lockout
- Sessions can be listed and ended, and an account keeps one session by default
Video and secrets
- Video is delivered with short-lived signed tokens, each for one action on one camera
- Camera credentials are encrypted at rest with AES-256-GCM and never returned to the console
- Logs never carry secrets, tokens or full stream addresses
- Requests to addresses a user supplies go through an outbound policy, which blocks private addresses unless you allow them
Accountability
- Every privileged action is written to an audit trail that can be filtered and exported
- Live and recorded viewings are logged with the person, the camera and the duration
- Retention and storage-limit purges are audited with the count, the bytes and the period
Who watched what, on the record
Every privileged change and every viewing, live or recorded, is logged with the person, the camera, how long and the address, and exports as CSV.

Each person sees only their cameras
Roles, per-camera grants, two-step verification, single sign-on, and accounts that expire on a date.

What the stack does in your account
The AWS Marketplace template is written so that a default launch is a closed one.
Encrypted storage
The recording bucket and the data volume are encrypted. The bucket blocks all public access and accepts only HTTPS.
No open management port
Shell access is through AWS Systems Manager Session Manager. SSH is closed unless you give the stack a range and a key pair, and the whole internet is refused.
A security group you define
The console and the live-video port open only to the address range you name. There is no default.
Least privilege on the instance
The instance role reaches its own bucket, secret, topic and volume and no other. Only the server container can read the role's credentials.
A first password that is not left lying around
It is generated on the instance, held in Secrets Manager, and kept out of the system journal and the support bundle.
Images checked before release
AWS Marketplace machine images are checked for known vulnerabilities before they are published, and operating-system security updates apply themselves.
Nothing is sent to HabileLabs
No video, no camera list, no usage report. On AWS Marketplace the subscription is the licence, so the appliance has nothing to check in with. Even the support bundle you may choose to send us carries no video, no credentials and no database contents.
The appliance connects out only to
- Your cameras
- Your own S3 bucket
- The notification services you configure
- Ubuntu and Docker package mirrors, for security updates
What we do not claim
No certification is claimed
HabileLabs holds no ISO 27001 or SOC 2 certification for Habile iEYE, and this site does not claim one. What is described here is how the software is built.
The default certificate is for trials
The appliance's self-issued certificate lets you sign in on the first minute. For regular use give it a host name for Let's Encrypt, or install your own certificate.
You operate it
On AWS you own the instance, its security group, its backups and the decision to update. That is the price of the video staying in your account.
Reporting a vulnerability
Report a suspected vulnerability privately, never in a public channel: to the HabileLabs security contact named in your support contract, or to support@habilelabs.io. Include the version, the component, the steps to reproduce and the impact you see.
Who builds it
HabileLabs is an AWS Advanced Tier Services Partner with the AWS AI Services and SMB Services Competencies. Those are the company’s AWS Partner tier and competencies, not a certification of Habile iEYE.
Bring your security team
We will walk your reviewers through the tenancy model, the media tokens and the AWS template line by line, and answer the hardening checklist for your environment.
Or email support@habilelabs.io · Monday to Friday, 10:00–19:00 IST
- Subscribe on AWS Marketplace30 days with no software charge on one instance; AWS bills the instance and storage.
- Launch the stackPick a Region and a size. A working console in about six minutes.
- Add your camerasGive the stack a route to your site (a VPN, Direct Connect or a peered VPC) and add each camera by its address.



