Campus Community recognises that the confidentiality, integrity and availability of information and data created, maintained and hosted by us are vital to the success of the business and privacy of our partners.

As a service provider/product, we understand the importance in providing clear information about our security practices, tools, resources and responsibilities within Campus Community so that our customers can feel confident in choosing us as a trusted provider.

This Security Posture highlights high-level details about our steps to identify and mitigate risks, implement best practices, and continuously develop ways to improve.

|
|

Controls (24)

Here are the controls implemented at Campus Community to ensure compliance, as a part of our security program.

Product security (2)

Production System User Review

Entity's Infosec officer reviews and approves the list of people with access to production console annually

Situational Awareness For Incidents

Entity maintains a record of information security incidents, its investigation, and the response plan that was executed in accordance with the policy and procedure defined to report and manage incidents.

Data security (8)

Identify Validation

Entity ensures that logical access provisioning to critical systems requires approval from authorized personnel on an individual need or for a predefined role.

Termination of Employment

Entity ensures logical access that is no longer required in the event of termination is made inaccessible in a timely manner.

Encrypting Data At Rest

Entity has set up cryptographic mechanisms to encrypt all production database[s] that store customer data at rest.

Inventory of Infrastructure Assets

Entity develops, documents, and maintains an inventory of organizational infrastructure systems, including all necessary information to achieve accountability.

Data Backups

Entity backs up relevant user and system data regularly to meet recovery time and recovery point objectives and verifies the integrity of these backups.

Testing for Reliability and Integrity

Entity tests backup information periodically to verify media reliability and information integrity.

Transfer of PII

Entity ensures appropriate procedures are in place to ensure compliance with regulatory requirements related to transfer of personal data outside of the region from which it is collected

Inventory of Personal Data (PD)

Entity maintains an inventory of categories of personal information collected along with its usage, sources and specific purposes for collection as per regulatory requirements ("Record of Processing Activities") and reviews it on an annual basis

Network security (5)

Limit Network Connections

Entity ensures that the production databases access and Secure Shell access to infrastructure entities are protected from public internet access.

Transmission Confidentiality

Entity has set up processes to utilize standard encryption methods, including HTTPS with the TLS algorithm, to keep transmitted data confidential.

Anomalous Behavior

Entity's infrastructure is configured to review and analyze audit events to detect anomalous or suspicious activity and threats

Data used in Testing

Entity ensures that customer data used in non-Production environments requires the same level of protection as the production environment.

Centralized Collection of Security Event Logs

Entity's infrastructure is configured to generate audit events for actions of interest related to security for all critical systems.

App security (4)

Conspicuous Link To Privacy Notice

Entity displays the most current information about its services on its website, which is accessible to its customers.

Secure system modification

Entity has procedures to govern changes to its operating environment.

Approval of Changes

Entity has established procedures for approval when implementing changes to the operating environment.

Unauthorized Activities

Entity uses Sprinto, a continuous monitoring system, to alert the security team to update the access levels of team members whose roles have changed.

Endpoint security (5)

Malicious Code Protection (Anti-Malware)

Where applicable, Entity ensures that endpoints with access to critical servers or data must be protected by malware-protection software.

Full Device or Container-based Encryption

Where applicable, Entity ensures that endpoints with access to critical servers or data must be encrypted to protect from unauthorized access.

Endpoint Security Validation

Entity has set up measures to perform security and privacy compliance checks on the software versions and patches of remote devices prior to the establishment of the internal connection.

Session Lock

Entity ensures that endpoints with access to critical servers or data are configured to auto-screen-lock after 15 minutes of inactivity.

Endpoints Encryption

Entity requires that all critical endpoints are encrypted to protect them from unauthorized access.

Create your own Trust Center | Powered by

Sprinto Logo