Creatrix Campus Infrastructure and Cloud Platform Security - v1.1
Creatrix Campus Infrastructure and Cloud Platform Security - v1.1
Disclaimer:
The following description about the general product direction is for informational purpose. Anubavam makes
no commitment of any kind, either express or implied, to deliver any material, code, or functionality for a
particular purpose, or of any other nature are made with respect to the development, release, and timing of
any features or functionality of the Creatrix’s product to which information mentions.
1. Introduction
2. Control: Security mechanisms to control who can access data and under
which conditions.
5. Security: Services that are designed, coded, tested, deployed, and managed
securely.
1. Infrastructure Security
• Our power systems with conditioned power protecting against sags, surges,
swells, spikes and electrical noise.
• Uninterrupted power supplies (UPS) with instant failover plans for continuity
during a power outage.
• Diesel generators to pick up the load quickly during extended outages.
• ISO 2700
• ISO 27001
• SSAE1
• SOC 1
• SOC 2
• SAFE HARBOR
4. System Security
The Creatrix Campus platform supports Single Sign On (SSO) and integration
with various authentication solutions including Active Directory, LDAP and
SAML/Shibboleth. Additionally, User ID and Password credentials from any
third-party system can be synchronized with Creatrix Campus local
authentication via the API.
For Creatrix Campus, passwords are never stored in plain text. Passwords are
securely hashed via the SHA-512 cryptographic hash algorithm with a
These network boundary devices employ traffic flow policies, or access control
lists (ACLs), that enforce the flow of traffic. Firewalls are deployed in a layered
approach to perform packet inspection with security policies configured to
filter the packets based on protocol, port, source, and destination IP address to
identify authorized sources, destinations, and traffic types.
User uploaded files are stored with unique names and folders in the Files
repository under a storage server. Institution’s admin will have an option to
encrypt and store the uploaded files with hash algorithm and a randomly
generated "salt" value. All file download requests require unique authorization
keys.
Application logs record the creator, last updated, timestamps, and originating
IP address for every record and transaction completed. Application passwords
are not accessible by Anubavam's persons.
Before allowing the user to see anything or save anything, their permission
capabilities are verified. Each permission capabilities are annotated with the
appropriate risks. If appropriate, restriction is enforced according to group user
roles.
Backup of databases are taken hourly, and each hourly backup is retained for
3 days, daily database backups are taken and retained for 3 months. Weekly
snapshots are taken and retained for a month. Monthly snapshots are taken
and retained for a year.
5. Data Segregation
The Creatrix system restricts access to objects based on the user ID and
tenant. When a user requests data, the system automatically applies an
institution filter to ensure it retrieves only information corresponding to the
user’s institution.
To ensure that your data remains protected in storage server, you can enable
encryption of the data in Creatrix Campus. Data encryption in Creatrix Campus
is done using a symmetric key, which is stored in a database and is encrypted
by using an public/private key pair.
When a file is stored in Creatrix Campus, it is first stored in the local disk cache
in its original form. The file is encrypted before it is uploaded to Storage Server.
When a file is retrieved from Creatrix Campus Storage Server, the data is
decrypted while it is being streamed to the local disk cache.
To enable encryption for a file system, you must select the Enable Encryption
All data traffic in and out of Creatrix Campus is encrypted using TLS to ensure
that no vulnerabilities are present.
• Strong authentication, data privacy, and integrity - TLS can help to secure
transmitted data using encryption. It also authenticates servers and, optionally,
authenticates clients to prove the identities of parties engaged in secure
communication. It also provides data integrity through an integrity check value.
In addition to protecting against data disclosure, it’s used to help protect
against masquerade attacks, man-in-the-middle or bucket brigade attacks,
rollback attacks, and replay attacks.
8. Data Backup
Backup of databases are taken hourly, and each hourly backup is retained for
3 days, daily database backup are taken and retained for 3 months. Weekly
snapshots are taken and retained for a month. Monthly snapshots are taken
and retained for a year.
9. Disaster Recovery
The Creatrix Campus platform supports Single Sign On (SSO) and integration
with various authentication solutions including Active Directory, LDAP and
SAML/Shibboleth.
The Creatrix Campus platform supports Single Sign On (SSO) and integration
with various authentication solutions including Active Directory, LDAP and
SAML/Shibboleth. Single Sign-On (SSO) is configured at the Institution level.
SSO gives the institution full control over which users are authenticated and
how that authentication is performed.
For customers who wish to use Creatrix’s native login, Creatrix only stores their
password in the form of a secure hash as opposed to the password itself.
12. Authorization
www.creatrixcampus.com | [email protected]
www.facebook.com/CreatrixCampus www.twitter.com/creatrixcampus
www.linkedin.com/company/creatrix-campus