Security & Reliability
The security approach, shared responsibilities, incident channels and contractual reliability information relevant to your deployment.
On this page
1. Security across the service lifecycle
InnuCloud uses a defense-in-depth approach for MigiHub, combining governance, access controls, secure development, infrastructure safeguards and operational monitoring. Controls are assessed against the risks and sensitivity of the service.
This overview helps with due diligence. Your agreement, security schedule and SLA define the controls and commitments applicable to your deployment. Ask for supporting evidence when evaluating a requirement.
2. Identity and access
Access is organized around authorized roles and least privilege. Relevant capabilities include SSO support, password and session policies, restricted administration, auditability and optional identity or network restrictions where supported.
Customers must review user access, remove departed users, protect privileged accounts and configure authentication options appropriate to their risk. Authentication features depend on the subscribed service and connected identity provider.
3. Data and infrastructure protection
Measures include TLS in transit, encryption of designated production data stores, restricted secrets and key access, logical customer separation, data minimization and infrastructure protections. Hosting and service-provider responsibilities are defined for the applicable environment.
Confirm primary, backup and support-access locations in the relevant agreement rather than assuming every connected service uses the same jurisdiction.
4. Secure development and monitoring
The security lifecycle includes code review, input validation, dependency and vulnerability management, configuration hardening, change control and staged deployment. Logging, alerting and abuse protections support investigation and response.
Security logs and administrative audit trails are handled under applicable retention and access policies. A public overview does not expose detailed defensive configurations or customer information.
5. Backups, availability and recovery
Backup and recovery practices include protected backups, retention schedules, restoration procedures and continuity planning. Performance and maintenance practices support the service’s availability.
Availability targets, support escalation, backup frequency, recovery point objective (RPO) and recovery time objective (RTO) are defined in the applicable SLA. No 99.9% uptime or 24-hour recovery commitment is promised by this page. Planned maintenance is communicated when practical; urgent protective maintenance may require immediate action.
6. Incidents and vulnerability reports
Security events are assessed, contained and investigated through incident-response procedures. Affected customers receive notifications and available information as required by the agreement and law. Standard support is Monday–Friday, 08:00–17:00, excluding holidays; additional emergency arrangements follow the contracted escalation process.
Report suspected vulnerabilities to security@migihub.com. Include affected URLs, minimal reproduction steps and non-sensitive evidence. Do not access another customer’s data, exfiltrate information, disrupt service, conduct social engineering or test production without written authorization. Reporting an issue does not grant testing permission.
7. Assurance, suppliers and customer controls
Request the applicable DPA, security schedule, subprocessor information and available assurance documents for procurement review. ISO certification and SOC reports are entity-, scope- and date-specific; neither a framework reference nor a cloud provider’s report proves MigiHub certification. This site does not claim an unverified certification.
Customers should configure access, minimize sensitive information, review integrations, maintain their own devices and training, and agree retention and recovery requirements. General questions: support@migihub.com. Privacy: info@innucloud.com.