Website Security and Account Permissions: Understand These 6 Key Concepts First

Most website security incidents aren't caused by sophisticated attacks, but by weak passwords, excessive privileges, and missing logs. Implementing these six co…

Insights:Website Security and Account Permissions: Understand These 6 Key Concepts First

Concept 1: Authentication (Who You Are)

  • Account passwords, verification codes, two-factor authentication.
  • Default credentials must be changed and never hard-coded in source code.
  • Avoid well-known paths for the admin panel login.

Minimum requirement: Admin accounts must be separate from front-end users, with strong passwords rotated on a regular schedule.

Concept 2: Authorization (What You Can Do)

  • Role separation: admin, editor, reviewer, read-only.
  • Each role's accessible menus and data must be clearly defined.
  • Deactivate unused accounts promptly.

Common issue: Granting everyone admin privileges makes it impossible to trace incidents back to individuals.

Concept 3: Least Privilege

  • Database accounts should receive only the permissions they need (read/write separation, per-database grants).
  • Do not run web services under the root account.
  • File and directory permissions should be opened only as needed.

Principle: give the minimum required; request more when necessary.

Concept 4: Session Management

  • Generate a new session ID after login to prevent session fixation.
  • Sessions expire automatically after a period of inactivity.
  • Logging out destroys the server-side session immediately.
  • Set Cookie flags to HttpOnly, Secure, and SameSite.

Concept 5: Audit Logging

  • Log logins, password changes, publishing, deletions, and permission changes.
  • Logs must include timestamp, account, IP address, and target object.
  • Regular accounts must not be able to delete logs.
  • Maintain logs for the retention period required by compliance.

Without logs, you cannot pinpoint the cause after an incident.

Concept 6: Backup Isolation

  • Backups must not reside on the same machine or in the same directory as the site.
  • Backup accounts must be separate from site accounts.
  • Verify recoverability on a regular schedule.
  • At least one copy of critical data must be kept offline or off-site.

Principle: If backups can be encrypted alongside your data by ransomware, you effectively have no backups.

Six Concepts: Implementation Order

  1. Change default passwords and restrict admin panel access.
  2. Define roles and enforce least privilege.
  3. Configure session security and timeouts.
  4. Enable audit logging.
  5. Set up isolated backups.
  6. Conduct regular self-checks (quarterly).

Common Mistakes

  • Admin password never changed in a year, shared among multiple users.
  • Database accounts given root-level permissions.
  • Logs retained for only 7 days, making incidents impossible to investigate.
  • Backups stored in the same directory, deleted along with everything else.

Scope & Limitations

The six concepts cover foundational protection but do not constitute a complete security system. Sites handling payments or member data also require code audits, vulnerability scanning, and penetration testing.

Related Articles: