AWS Cloud is used https://aws.amazon.com/compliance/
Yes, we conduct internal penetration tests either every 3 months or after every major release.
Yes, internally, every 3 months, or major release - whichever comes faster.
Yes, AWS data is anonymized. AWS IAM Policy is in place to prevent data access.
Yes, customer data is purged with Customer or Camera deletion. The integrator has control over deletion.
Yes, AWS VPC is used to separate environments. No on-premise staging environment is used.
Yes, AWS data is anonymized. AWS IAM Policy is in place to prevent data access.
Yes, no 3rd party access to AWS cloud infrastructure. AWS GuardDuty is used.
No, all data is always stored on AWS servers.
Yes, AWS SecuirtyHub is used. https://aws.amazon.com/compliance/
Yes, AWS cloud.
Yes, the AWS IAM policy is used.
Yes, AWS CloudTrail and SecurityHub.
Yes.
Yes, AWS encryption is at rest at applicable services used. For footage, AWS S3 server-side encryption AE-256 is used.
Yes, in case of 3dEYE PUSH technology a secure SSL tunnel is created between the camera and the cloud. AES-256 is used.
Yes, the latest AWS AMI based on AWS ECS ASG, Fargate and AWS Serverless architecture is used.
Yes, On critical vulnerability AWS will recall AMI. AWS ECS and AWS serverless infrastructure will re-deploy.
Yes, AWS WAF, AWS GuardDuty, the latest AWS AMI, ECS, and AWS serverless architecture are used.
Yes.
Yes, AWS SecurityHub, AWS Guard Duty, AWS CloudTrail.
Yes, AWS data is anonymized and not available. Customers can review application logs in the 3dEYE platform admin panel related to a specific customer.
Yes, AWS IAM policy is used, AWS GuardDuty, AWS CloudTrail.
No.
Yes. Separate, personalized Private Cloud installation can be used to ensure logical segmentation.
Not applicable. We don’t store, process, or access Customers' intellectual property.
Yes, the Public cloud is available in the US and Europe AWS region. Personalized Private Cloud installation can be located in any AWS region and zones including GovCloud.
Yes.
Yes.
Yes, the Customer can save video footage clips in Library for evidence. Such footage won't be deleted unless the Camera or Customer is deleted.
Yes, In case the customer creates an Alert schedule, AI Video analytics will access customer footage to produce relevant events.
No.
Yes, AWS SAML, OAuth2 is available for integrations.
Yes, MFA is available for end-users.
Yes, AWS IAM policies and MFA is used.
Yes.
Yes, AWS SSM and SecretsManager are used. AES 256 or AWS service relevant cipher.
Yes.
Yes, AWS IAM and SecretManager are used.MFA is Mandatory.The minimum password length is 8 characters.Require at least one number.Require at least one non-alphanumeric character (! @ # $ % ^ & * ( ) _ + - = [ ] { } | ').Allow users to change their own password.Remember the last 3 password(s) and prevent reuse.
Yes. 3dEYE has integrated a risk and compliance program throughout the organization. This program aims to manage risk in all phases of service design and deployment and continually improve and reassess the organization’s risk-related activities.
Yes.
Yes.
3dEYE leverages AWS Security and Compliance tools https://aws.amazon.com/products/security/
Yes. https://aws.amazon.com/products/security/
Annual or change related to employee status.
Yes.
3dEYE leverages AWS Detection, AWS Network, AWS application protection tools, GitHub security and vulnerability tools, and Microsoft security tools. AWS Services, such as GuardDuty, provide us with continuous monitoring for malicious activity and unauthorized behavior.
3dEYE leverages AWS snapshot and backups https://aws.amazon.com/backup/Services/ are redundant. AWS Serverless architecture is used. Backups and snapshots storage duration and recurrency are service dependent. For instances is usually daily recurrence snapshots.
3dEYE leverages AWS Detection, AWS Network tools https://aws.amazon.com/products/security/?nc=sn&loc=2
Yes, we conduct internal penetration tests either every 3 months or after every major release. 3dEYE performs load tests and code inspections on every new version build. 3dEYE follows AWS Well Architected framework and respective AWS tools. https://aws.amazon.com/architecture/well-architected/
Yes, we conduct internal penetration tests either every 3 months or after every major release. 3dEYE performs load tests and code inspections on every new version build. End-user UI (web/mobile) is checked against the common vectors of attacks.
Yes.
3dEYE exercises mandatory policy to move to new framework versions. The latest updated libraries during the build process are used. Best practices during the development process are followed. Standard libraries and approaches to encryption, authentication and authorization are used. 3dEYE performs load tests and code inspections on every new version build. End-user UI (web/mobile) is checked against the common vectors of attacks. Extraneous content on the client is blocked using CSP headers.
3dEYE utilizes AWS Encryption. Every AWS Service where data lands provide Encryption at rest and in transit.
AWS Incident Management services are used. https://aws.amazon.com/products/security/?nc=sn&loc=2
Yes. AWS D/CP is leveraged: https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-options-in-the-cloud.html
Annually or after major infrastructural changes. AWS Config is used continuously to monitor and record AWS resource changes. AWS CloudFormation is used to automate tests. https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-options-in-the-cloud.html
Yes, annually or during new region acquisition and expansion.
Yes.
Yes, 3dEYE leverages AWS Automated Incident Response and Forensics Framework, AWS Incident Response.
3dEYE leverages respective guidelines and policies. AWS Security and Compliance tools https://aws.amazon.com/products/securityAWS/ FTR program AWS Well Architected Framework and toolset https://aws.amazon.com/architecture/well-architected/
3dEYE employs a comprehensive suite of AWS tools and services to facilitate GDPR compliance for its clients. Furthermore, 3dEYE has strategically deployed its infrastructure within the AWS Stockholm datacenter, thereby ensuring data storage within the geographical confines of the European Union. This meticulous approach underscores our commitment to data security and regulatory adherence. More info: https://aws.amazon.com/blogs/security/all-aws-services-gdpr-ready/