SECURITY
Security belongs in the platform architecture.
Hamiltonn Cloud treats security as a combination of identity, access control, application boundaries, operational controls and disciplined change rather than marketing badges.
Hamiltonn Cloud
Security belongs in the platform architecture.
Hamiltonn Cloud security is the set of technical and operational controls used to protect supported platform services, customer environments and data access.
Definition
What does this mean?
Hamiltonn Cloud security is the set of technical and operational controls used to protect supported platform services, customer environments and data access.
Hamiltonn Cloud combines reusable software infrastructure, configurable product capabilities and flexible deployment so organisations can build around their own brand and operating model.
CONTROL AREAS
Security is layered.
Identity & access
Authentication, roles, permissions and privileged-access boundaries.
Tenant boundaries
Keep customer context enforced below the frontend.
Application security
Validation, controlled APIs and protected administrative actions.
Secrets
Protect credentials and environment configuration.
Operational security
Monitoring, patching, incident handling and controlled deployment.
Data protection
Appropriate transport, storage and backup protection.
SHARED RESPONSIBILITY
Hamiltonn secures its platform scope; customers secure what they control.
Customers remain responsible for staff access decisions, their devices and networks, customer-facing business processes and systems outside the Hamiltonn-managed boundary.
CHANGE
Security changes should move through controlled delivery.
Develop
Implement the change.
Test
Run validation.
Stage
Exercise the release where applicable.
Approve
Apply required gates.
Deploy
Promote through the release process.
Observe
Verify health and investigate anomalies.
REPORTING
Report suspected vulnerabilities responsibly.
CERTIFICATIONS
Publish certifications when they are actually held.
Hamiltonn Cloud does not use unearned certification badges. Formal certifications should be published with evidence when achieved.
FAQs
SECURITY FAQs
Does Hamiltonn claim SOC 2 or ISO 27001 certification?
Hamiltonn should only claim certifications that are actually held and documented.
How are tenant boundaries enforced?
Tenant context should be enforced in platform services and access controls rather than trusted to the frontend.
Who manages customer staff permissions?
Hamiltonn provides permission capabilities; the customer decides which users receive access.
How should a vulnerability be reported?
Use the Hamiltonn Responsible Disclosure route.
Does Dedicated Enterprise change security?
It can add customer-specific infrastructure boundaries while application and operational controls remain necessary.
Build on Hamiltonn Cloud.
Choose the product, modules and deployment model that fit your business, then bring the customer experience under your own brand.