Rigo Security Centre Secure-by-design IoT solutions, built around global cybersecurity compliance. Connected devices naturally face cybersecurity challenges that require robust safeguards. At Rigo, security is engineered into hardware, firmware, and cloud services from design through operations. This Security Centre outlines our standards, testing, and update practices: secure-by-design development, encrypted communications, strong authentication, hardened configurations, and fleet management via IIot Cloud. Our program aligns with CRA, NIS2, ISO/IEC 27001, and IEC 62443. We perform ongoing security testing, run a coordinated vulnerability disclosure process, and deliver timely firmware and software updates. The result is enterprise-grade assurance you can trust at scale. Explore resources, current certification status, and reporting channels below.
How We Test So You Can Deploy With Confidence:
Security at the edge is too important to leave to chance. This section shows, step by step, how Rigo tests products before they reach your network turning requirements and threat models into real tests, validating fixes, and proving results with independent penetration testing and clear advisories. The outcome for you: fewer surprises in the field, faster approvals with IT and compliance, and a platform you can trust at scale.
1. Security Requirements Testing Before any release, we verify that security is designed, implemented, and stable under real workload. Teams test core security functions, performance and scale, edge conditions, malformed inputs, and trust boundaries so controls work under stress not just in a lab.
2. Threat Modeling Validation We turn the threat model into action. For every identified threat, we test that the mitigation works as intended, then we try to defeat it with the same techniques an attacker would use.
3. Vulnerability Discovery We look for weaknesses the way attackers do. Automated and manual fuzzing, protocol abuse, and high-load scenarios probe every external interface, while an attack-surface review finds weak ACLs, exposed ports, and services running with unnecessary privileges.
4. Independent Penetration Testing An external team performs black-box testing on a recurring schedule and at project milestones that allow time to fix and re-test. Findings are prioritized, mitigated, and verified before wide release.
5. Issue Documentation and Assessment Every confirmed issue is recorded with time, location, scope, and reliable reproduction steps. We analyse root cause and user impact, assign severity, and prioritise the fix so the most important risks are addressed first.
6. Remediation and Verification Fixes follow a plan and schedule. Code changes undergo security review, QA validates effectiveness, and we re-run relevant security tests to ensure the issue is resolved without introducing new ones.
7. Release and Responsible Disclosure We choose the right release path: normal, interim, or emergency. Security notes and deployment guidance are updated, and when disclosure is appropriate, we publish advisories with mitigation steps and timelines. Post-release monitoring confirms stability in the field.
8. Continuous Improvement We learn from patterns. Trends in findings shape future requirements, test methods, and training. Threat models are updated as features evolve so the security design stays aligned with the product.
