7 Security Checks to Run Before Giving a Developer Access to Your Business Website
Hiring a developer to update a website, fix a problem or add new features often requires access to parts of the business’s online systems. However, sharing access without checking how it is managed can expose customer information, business accounts and website operations to unnecessary risks.
For small businesses and startups in South-East Nigeria, these seven checks can help protect a website while allowing a developer to do the work required.
1. Create a Separate Account for the Developer
A developer should have an individual account with the permissions needed to complete the assigned work, rather than using the business owner’s personal login.
Sharing one account makes it difficult to identify who performed an action and creates problems when access needs to be withdrawn. If the account also controls email, payments or other business services, the exposure can extend beyond the website.
What to do: Create a separate developer account in your website’s content management system or hosting platform. Use role-based permissions to limit what the account can change. For example, a developer fixing page layouts may not need permission to manage payments or view customer records.
2. Enable Multi-Factor Authentication
Multi-factor authentication (MFA) requires an additional verification step beyond a password when someone signs in. This can help protect an account if its password is stolen or exposed.
Website administrators and hosting accounts are particularly important because they may allow users to change website content, install software or access sensitive settings.
What to do: Enable MFA on the hosting account, website administrator accounts, domain registrar and any other service that supports it. Ask the developer to secure their individual account as well. Prefer an authenticator app or security key where supported, and store recovery codes securely.
3. Check What the Developer Can Access
Website access does not always stop at the website itself. Depending on the setup, a developer may also be able to access databases, customer information, payment integrations, domain settings or the business’s cloud infrastructure.
Giving someone more access than the job requires increases the number of systems that could be affected if their account is compromised or misused.
What to do: List the systems required for the project and grant only the necessary permissions. If a developer is updating website content, they may not need access to the production database or payment dashboard. Review permissions before expanding them.
4. Back Up the Website Before Work Begins
A backup is a recoverable copy of the website’s files, database and relevant configuration. It can help restore the site if an update fails, data is accidentally deleted or a security incident damages the system.
Without a usable backup, a seemingly small change can cause extended downtime or the loss of business information.
What to do: Create a fresh backup before major changes, including the database and website files where applicable. Store a copy separately from the main website account and check that the backup can actually be restored. A backup that has never been tested should not be treated as a guaranteed recovery plan.
5. Keep Passwords, API Keys and Other Secrets Private
Developers sometimes need technical credentials to connect a website to a database, email service or payment provider. These credentials can grant access to systems beyond the website if they are exposed.
Putting passwords, database credentials, API keys or secret tokens directly into source code can also leave them in version-control history, including repositories that later become public.
What to do: Share credentials through an appropriate secure method, use environment variables or a secrets manager where suitable, and avoid sending sensitive details in public repositories or ordinary project documents. Give each developer only the credentials needed for the task. If a secret is exposed, revoke or rotate it promptly rather than simply deleting the visible copy.
6. Set an Expiry Date for Access
Developer access should match the duration and scope of the work. An account that remains active long after a project ends creates an unnecessary route into the business’s systems.
This matters even when the developer is trusted. Projects end, working relationships change, and accounts can be forgotten or compromised.
What to do: Agree on when access will be reviewed or withdrawn. Once the work is complete, remove unnecessary accounts, revoke temporary credentials and access tokens, and review any changes to administrator permissions. If the developer provides ongoing maintenance, keep only the access required for that continuing responsibility and review it periodically.
Discover more from Scalepoint Africa
Subscribe to get the latest posts sent to your email.