On this page
THE DIRECT ANSWER
Start security planning with the accounts, people, and data involved. Use appropriate sign-in protection, limited permissions, maintained software, and a recovery process that the business can actually operate.
Know who controls each account
Record the business owner of the domain, hosting, email, and application administration. Use named access where practical and avoid a shared login that cannot be attributed to a person. Review access when a staff member or supplier no longer needs it.
Match permissions to the task
A content editor may not need to change users, payment settings, or server configuration. Separate routine publishing from high-impact administration. Use suitable authentication protections, including multi-factor authentication where supported, and plan account recovery before someone loses access.
Keep operational checks in the maintenance plan
Identify who handles software updates, suspicious activity reports, and security-related incidents. Protect private information through appropriate controls rather than assuming it is hidden because its URL is difficult to guess. Avoid publishing credentials in page code, documents, or public repositories.
An illustrative business scenario
A marketing team can receive publishing access while domain and hosting ownership remain with the business. A departing contractor's access can then be removed without forcing every editor to share a replacement password.
A practical checklist
- Inventory important website accounts.
- Use appropriate individual access.
- Limit permissions by responsibility.
- Document recovery and incident contacts.
Questions about this topic
Does HTTPS make a website completely secure?
No. It protects communication in transit when correctly configured, but access, application behaviour, software, and data handling still need attention.
Should a developer keep the only administrator account?
The business should have an agreed ownership and recovery arrangement. A single untransferable supplier account creates an operational dependency.
Further reading
Plan your next website step.
Discuss your business, the visitor journey, and the work you need with Web Developer Jakarta. A short brief can help start a useful conversation.
Discuss Your Website ↗