Share Registry Portal (HK) Security Protocols

Modified on Sun, 27 Jul at 12:44 PM

Overview 

At Share Registry Portal (HK), we are dedicated to building trust through robust security, privacy, and reliability in our platform. Our Trust Center is designed to provide complete transparency into how we protect your data and ensure seamless, secure operations for users of this portal. By adhering to industry-leading standards, implementing stringent security protocols, and maintaining clear data governance policies, Share Registry Portal (HK) empowers users to view information and perform actions confidently. The Trust Center outlines our commitment to safeguarding your information, ensuring compliance, and fostering a trusted environment for users of this portal.

 

TABLE OF CONTENTS

 

What are the certifications of Share Registry Portal (HK)?  

Security Certifications at Issuer Portal 

At Issuer Portal, we prioritize the security, integrity, and compliance of your data.

Our Certifications 

The infrastructure and data centre services of Share Registry Portal (HK) is covered under ISO/IEC 27001. This certification is renewed continuously. 

The most recent certification was issued in 2023. 

 

What is the Encryption Method? 

Data Encryption at Share Registry Portal (HK) 

At Share Registry Portal (HK), safeguarding your data is a top priority. Our platform, hosted on Microsoft Azure infrastructure, employs robust encryption methods to protect information, ensuring your data remains secure throughout its lifecycle. 

 

To protect data in motion, our web application uses HTTPS. This ensures all communications between users and the platform are encrypted, preserving data confidentiality and integrity during transmission. 

 

What is Security Testing & Risk Management?

 
Penetration Testing and Vulnerability Management 

Share Registry Portal (HK) conducts annual third-party penetration testing to assess and strengthen the security of our platform and supporting infrastructure. These assessments are performed by independent security experts using industry-standard methodologies. 

 
All critical and high-risk findings are addressed immediately upon discovery. Medium vulnerabilities are tracked and resolved as part of our regular release cycles within the same calendar year. We document all findings and remediation steps to ensure full traceability and follow-through. Summary reports are available upon request under a non-disclosure agreement.

What is Backup Policy?


All databases on server are backup based on Business Continuity Plan.   

These backups require no manual intervention and are automatically managed, monitored, and retained. 

 

What are Share Registry Portal (HK) Incident Response Plan? 


Disaster Recovery at Share Registry Portal (HK) 

At Share Registry Portal (HK), we are committed to ensuring the continuity and security of your operations. Our comprehensive Disaster Recovery (DR) Plan is designed to minimize downtime and data loss in the event of an unplanned incident, enabling rapid restoration of services. 

Disaster Recovery Plan 

Our DR Plan outlines well-defined procedures for recovering critical systems and data. Two key metrics guide our response: 

  • Recovery Time Objective (RTO): The maximum acceptable downtime for systems, applications, or networks. 
  • Recovery Point Objective (RPO): The maximum acceptable period of data loss during an incident.

The DR scope includes restoration of both our Azure-hosted platform and database, ensuring end-to-end service continuity. 


 We’re committed to maintaining your trust through transparency and robust security practices. If you have any questions or need further assistance, please raise a ticket, and our support team will respond as soon as possible. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article