Shared responsibility in practice
Trust and security at HostGanga
Understand the customer and provider responsibilities that support safer hosting, account access, billing, domains, and incident communication.
- Shared-responsibility model
- Account protection habits
- Clear incident reporting
Security starts with clear ownership
Hosting security spans account identity, billing, domain control, network exposure, operating systems, applications, and data. HostGanga manages the portions defined by each service; customers remain responsible for their credentials, configurations, software, users, content, and recovery choices unless a written plan says otherwise.
This page avoids blanket certification or infrastructure claims. If your organisation has a regulatory, data-location, audit, encryption, or vendor-review requirement, request current written information that applies to the exact service you plan to use.
Account care
Use a unique password, protect email access, review authorised users, and verify sensitive requests through official channels.
Workload ownership
Patch customer-managed systems, limit exposed services, secure applications, and maintain restorable backups.
Responsible reporting
Send suspected abuse or security concerns with relevant timestamps, affected assets, and non-sensitive evidence.
Build a verifiable operating routine
Keep domain registrant details, recovery email, billing contacts, and technical owners current. Review access after staff changes. For VPS workloads, inventory public ports, software versions, secrets, certificates, backup jobs, and monitoring ownership.
- Do not share passwords or private SSH keys in messages
- Confirm requests that change ownership or payment details
- Test restoration rather than assuming a backup is usable
Ask precise questions before purchase
Security requirements should be matched to a named product, location, and management model. Ask who patches the guest operating system, what access and recovery tools exist, how data is deleted, and which optional protections can be configured. Current written answers are more useful than generic assumptions.
Security controls and responsibilities are product-specific; request current confirmation for formal requirements.
Frequently asked questions
Who secures software on my VPS?
For a customer-managed VPS, the customer generally manages the guest operating system and applications unless the purchased service explicitly states otherwise.
Where should I report a security concern?
Use the contact page and include the affected domain or service, time observed, impact, and safe reproduction details. Never send passwords or private keys.
Can HostGanga complete a vendor security questionnaire?
Contact the team with the exact service and questions. Responses depend on current, applicable evidence and may require commercial review.