The secure website is not only an SSL certificate. It needs a current environment, limited access, copies of the reproducible and response procedure. Most of these elements are invisible to the customer — until they stop working.
Updates and minimum area of attack
The system, libraries and server should have supported versions. Any unnecessary module increases the number of dependencies, so we delete unused extensions and accounts.
The update is preceded by a copy and test of key functions. Automatic implementation without return can be as risky as the lack of updates.
Accounts, passwords and permissions
Each person uses their own account. The permissions correspond to the task and the accounts of former employees are disabled. Wherever possible, we include multi-component authentication.
Access to domain, hosting, mail, analytics and CMS should not depend on a private account of one person. The company must know who owns each resource.
Backup and Playback
A copy of the database without files or files without configuration may not be enough. We set the frequency, retention, separate location and responsibility for playback.
The copy becomes reliable only after the restoration test. The result and the playback time should be documented.
Forms, data and monitoring
The form requires validation on the server side, protection against abuse and safe shipping. We only collect the data needed for the process and determine storage time.
Monitoring should detect inaccessibility, application errors, certificate problems and unusual logins. Logs must be protected and stored for a reasonable time.
Response plan for the incident
The team should know how to disconnect the endangered item, secure the evidence, change access, recreate the service and inform the relevant persons. List of contacts and owners shortens the response time.
After the incident, we analyze the cause and introduce a change to prevent repetition. Just restoring the copy does not solve the root of the problem.
Checklist
- Use supported versions and remove unnecessary modules.
- Give separate accounts and minimum permissions.
- Enable MFA for critical services.
- Test playing complete copies.
- Prepare a contact list and an incident procedure.
Check the account from the perspective of its task
It is not enough to list roles in the settings. Log in to the editor's example account and check the available actions. The account should allow you to perform an assigned task while not allowing unagreed changes to configuration or other resources.
Principle of the smallest powers described by the OWASP is to grant only the access needed for work. This also means control on the application side; hiding a button in the interface does not replace checking the permissions for operations.
Practice the situation without causing a malfunction
A short team exercise can be conducted: the form stops sending messages or the administrator loses access to the panel. Participants should determine who receives the notification, as confirmed by the problem and who can run the proper procedure. You do not need to disable the working page.
- Check availability of the current contact list.
- Determine where the instructions for reproduction are located.
- Confirm how to obtain emergency privileges.
- Write down who informs the team about the status of the service.
The exercise often reveals a dependence on one person or an outdated contact number. Such shortcomings are worth removing before the real problem arises.
Match Monitoring to Important Activities
Information that the server responds, does not confirm the operation of the order, form or integration. Choose the most important functions and determine how to control them. The tests should be prepared so that they do not create random orders, do not send mass messages and do not reveal the recipients' data.
Close the event only after checking the cause
Restoring the operation of the site is the first result, but a review of the cause is still needed. Save what happened, what actions have been taken and changed to limit the repetition. Not every problem will be a security incident; distinguishing the failure, configuration error and unauthorised action helps to select the correct response. The procedure is to be short and feasible by the team that actually takes care of the service.
The most common questions
Does SSL mean safe side?
SSL encrypts the connection, but does not protect against application gaps, weak passwords or data loss.
How often do I make a copy?
The frequency depends on how much data the company can lose. The store usually needs more copies than a static page.
Is the copyrighted CMS safer?
Not by definition. A lower number of dependencies and code control may be the advantage, but updates, tests and procedures are still needed.
Related BxM guides
