Loading...
Megabit Cloud
Megabit Cloud
Important information about using Megabit Cloud services.
Megabit Cloud is a brand of Gewape Cloud (Pty) Ltd, a company registered in South Africa with the business registration number 202287013807.
Our registered office is located in Johannesburg, Gauteng, South Africa.
Annex E: how the services are secured.
E1 Management system. The Service Provider operates an information security management system aligned with ISO/IEC 27001, with documented policies for access control, change management, incident response, business continuity and supplier management. It shall inform the Client on request of the certifications and attestations it holds. Nothing in this Agreement is a warranty that any certification will be obtained.
E2 Encryption. Client Data is encrypted in transit on all customer-facing endpoints and on administrative access, using TLS. Encryption at rest, and encryption with keys held by the Client, apply as stated in the Data Processing Agreement or the applicable Service Schedule.
E3 Tenant isolation. Each project or account of the Client is a separate isolation boundary with its own credentials. Access between projects is possible only through policies set by the Client.
E4 Administrative access. Access to the infrastructure used to provide the Services is limited to named personnel of the Service Provider, granted on the principle of least privilege, made over encrypted connections through the Service Provider's virtual private network with individual credentials, logged, reviewed at least once in every calendar quarter, and revoked within one (1) Business Day of a person ceasing to require it.
E5 Identity. Customer sign-in is through the Service Provider's single sign-on service, with email verification and multi-factor authentication. The Client controls who may use each project and at which level.
E6 Personnel. Personnel with access to Client Data or production systems are subject to clause 4.3.
E7 Physical security. The Services are hosted in controlled data center facilities with access control at the facility, uninterruptible power and standby generation (clause 10.2), and diverse network connectivity. Each facility maintains on-site fuel reserves for its standby generation, with arrangements for resupply during a prolonged outage of the public power supply.
E8 Monitoring and incidents. The Service Provider monitors the infrastructure and maintains a documented incident response procedure. Security Incidents are notified under clause 4.6.
E9 Vulnerabilities. Platform components managed by the Service Provider are maintained and patched under its change process. Following identification, the Service Provider shall remediate or mitigate vulnerabilities in those components within the following target periods, according to severity assessed by reference to a recognized scoring standard: (a) critical: fourteen (14) days; (b) high: thirty (30) days; (c) medium: ninety (90) days; and (d) low: in the ordinary maintenance cycle. A vulnerability that is being actively exploited is treated as an emergency under clause 4.5.
E10 Testing. Penetration testing and business continuity testing are carried out under clauses 4.7 and 10.3.
E11 Client responsibilities. The Client is responsible for the security of what it controls, as clause 5.3 provides.