Create Use Case Documentation (DOCU-176)

[DOCU-209] Security best practices Created: 09/Sep/11  Updated: 29/Jan/13  Resolved: 31/Oct/11

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Critical
Reporter: Antti Hietala Assignee: Ruth Stocks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Date of First Response:

 Description   

Write best practices and tips for Magnolia security. Examples:

  • Use physically separate permanent storage (databases) for author and public instances
  • Change the default superuser passsword!
  • You will eventually lock superuser out by accident. Fixes:
  • Create secure, usable passwords. Link to Usability of Passwords
  • Block the AdminCentral URI /.magnolia with Apache another Web server on a permanent basis for anybody else except users inside the local network. If you have authors outside the local network this is not appropriate.


 Comments   
Comment by Jan Haderka [ 19/Sep/11 ]

Already had 3 big customers requesting those guidelines in last 2 weeks.

Comment by Ruth Stocks [ 11/Oct/11 ]

Updated pages at:

Comment by Antti Hietala [ 11/Oct/11 ]

Feedback:

  • Page title is repeated as heading. Drop the heading.
  • Simplify language. In a technical writing register ambiguity doesn't usually help. "As a rule, it is advisable to store public and author databases in separate physical locations." It's OK to be direct and brief as long as you are correct.
  • Explain the "why" if you know. For example, why should author and public databases be on separate physical servers? Ask developers to validate your reasoning, or if you don't know the reason, ask them to explain. Not obvious to reader either.
  • Fourth bullet is incomplete. Anonymous access to ./magnolia and .magnolia/* should be blocked with an ACL on both author and public instances in any case. Access for authorized users such as editors should be permitted on author instance. The question is, why should a public Magnolia instance be fronted with Apache. There are many reasons why Apache is not needed so explain the security reason that trumps them.
  • Since these are best practices, link from Use cases.

Thanks!

Comment by Antti Hietala [ 31/Oct/11 ]

Added Zdenek's feedback on fronting Tomcat with Apache Web Server to Security best practices. Linked from Use cases.

Generated at Mon Feb 12 01:06:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.