No. SecureCircle can protect all file types and is independent of file extension.
Yes. Once files are protected by SecureCircle they are always trackable. No matter where files are stored, access logs are generated giving details on the IP address of the endpoint accessing the file, the application accessing the file, whether access was successful or failed, time of access and much more.
Yes, with SecureCircle files are always protected at rest, in transport and during use. Files are never in a decrypted state.
A Circle is a set of devices and users that have access to a set of files. Files, Users, and Devices can be added or removed from the Circle at any time.
SecureCircle supports device and user-based authentication. However, authentication can be centered around data classification types and not organizational units.
No, our solution is completely transparent to end users and only if users are violating policies will they be aware something has changed.
Yes and minimal. There is a 53 byte overhead when processing files with SecureCircle in addition to AES decryption; however, on most modern endpoints (Intel i3), this overhead has no perceived impact to users.
SecureCircle uses TLS and Open SSL AES-256 encryption and session-layer uses TLS over SSL applying 2048 bit keys. Strong AES-256 file encryption applies a unique key per file.
Yes. As long as the search and indexing application is in the “Allowed” list of applications.
Yes, we have contextual agents you can deploy at known egress points from any application. For example, these agents can be easily configured to protect data based on any combination of parameters such as: process name, time, location, endpoint type, size of file, location of endpoint, etc. If the created file matches the security criteria, then it will be automatically entered into a SecureCircle.
Yes. SecureCircle allows you to grant certain applications into the “Allowed” list so these applications are the only applications that can access the content of the protected files. Applications not in the “Allowed” list cannot decrypt secured data.
Yes, once a file is in a SecureCircle only controlled allowed applications can update secured files. Since a virus is not in the allowed list, it will not be able to modify the secured file.
SecureCircle’s Adaptive Source Protection can protect data base on context, content, user-based classification, server side scripting, and manual user ingestion. These method seamless apply to user workflows without having the user alter their work behavior.
No. There is no change to the user experience.
No. The file extension never changes. Files that are protected by SecureCircle are exactly the same as before they were protected; in fact, protected files are hash identical to the original file.
Yes, protected files can be stored and access over protocols such as SMB, CIFS, AFP, and DFS.
Yes, you can still use any file, sync and share utility to collaborate on protected files.
Yes, SecureCircle delivers a pure native experience on MacOS. For example, Mac users can still use the Mac Preview utility to open and view any type of file.
No they do not. Any application can work with SecureCircle without modification. Applications interface with protected files through the operating system API ; therefore, access to the file never changes.
Yes, SecureCircle generates system log files that can be used by most SIEM products including Splunk, Arcsight and QRadar. These systems can be set up to monitor for unusual file access activity such as successive access denied by the same process; in this case, it might be a virus trying to open a protected file.
Yes, SecureCircle has been deployed in many complex VDI environments including Citrix. Our solution integrates with Microsoft Active Directory or LDAP based directory services as well as works over SMB/CIFS/DFS connections so home folders can be remotely mounted and folder redirection enabled.
Yes. SecureCircle servers that are responsible for authentication and key management can be on-premise or in the cloud. These services may be deployed as a Docker container or a virtual machine.
Yes. SecureCircle integrates with Active Directory so you can manage user access to files using Active Directory Group Membership, regardless where the file is stored.
Yes. Once authentication is verified, you can work with files offline until the access token has expired. The token expiration is configurable.
Yes. You will need to install the SecureCircle iOS application; once installed, you can open protected files on your phone or tablet. Android will be supported early Q2.