Insights:How to Choose Website Security and Account Permissions: Solution Boundaries for Businesses of Different Sizes
Scenario 1: Small Single-Site Project (1–3 sites, 1–2 people on maintenance)
Core Risks: weak passwords, exposed admin panel, no backups.
| Item | Recommended Practice |
|---|---|
| Authentication | Strong password + change default login URL |
| Authorization | Two-tier: admin & editor |
| Session | HTTPS + timeout policy |
| Logging | Login and publishing records |
| Backup | One offsite or offline copy |
| External Assessment | Basic scan once per year |
Key point: Don't buy complex security products; get the basics right first.
Scenario 2: Medium Multi-Site Setup (4–20 sites, dedicated ops team)
Core Risks: messy permissions, scattered logs, cross-site impact.
| Item | Recommended Practice |
|---|---|
| Authentication | Unified account system, centralized management |
| Authorization | Role matrix, site-level access control |
| Session | Unified session policy |
| Logging | Centralized collection, retained for 90+ days |
| Backup | Unified backup policy and drills |
| External Assessment | Scan + spot check every six months |
Key: Unified and centralized, avoid having separate setups for each site.
Scenario 3: Sensitive Data / Transactions
Core Risks: Data breaches, unauthorized access, compliance requirements.
| Item | Recommendation |
|---|---|
| Authentication | Two-factor authentication |
| Authorization | Fine-grained permissions + approval workflow |
| Session | Short timeout + device management |
| Logs | Tamper-proof storage, retained for over 180 days |
| Backup | Encryption + off-site + regular drills |
| External assessment | Annual penetration testing + code audit |
Key: At this point security is a system — it requires dedicated ownership.
Tier Comparison
| Dimension | Small project | Medium | Sensitive / transactions |
|---|---|---|---|
| Account system | Manual | Unified | Centralized + two-factor |
| Logs | Basic logging | Centralized collection | Tamper-proof |
| Assessment frequency | Annual | Semi-annual | Annual (pen test) |
| Personnel | Part-time | Semi-dedicated | Dedicated |
| Risk of over-engineering | High (overbuying) | Medium | Low (must-do) |
Four Questions to Ask When Choosing
- Does the site contain customer personal information? Yes → at least a medium-sized plan.
- Is there payment or fund flow involved? Yes → follow the sensitive data plan.
- Can incidents be traced back? No → add logging first.
- Is there someone who can maintain it continuously? No → choose a simple, maintainable plan.
Common Misconfigurations
- A small site buys a full suite of security equipment but no one knows how to configure it — effectively, nothing is installed.
- Medium-sized sites use separate accounts per site, making it impossible to disable them all at once.
- A site with payment processing retains logs for only 7 days.
Boundaries
The plan ensures "risks are manageable," not "absolutely secure." Every solution requires ongoing maintenance and regular evaluation.
Related Reading: