Databases Reference
In-Depth Information
Include local_machines_only.conf
</Location>
<Location /confluence/spaces/importpages.action>
Include local_machines_only.conf
</Location>
<Location /confluence/spaces/flyingpdf/flyingpdf.action>
Include local_machines_only.conf
</Location>
<Location /confluence/spaces/exportspacehtml.action>
Include local_machines_only.conf
</Location>
<Location /confluence/spaces/exportspacexml.action>
Include local_machines_only.conf
</Location>
<Location /confluence/plugins/servlet/embedded-crowd>
Include local_machines_only.conf
</Location>
<Location /confluence/plugins/servlet/upm>
Include local_machines_only.conf
</Location>
This will make sure the administrative functions can only be accessed by the
specified machines and IPs.
Best practices
How you set up your Confluence roles, permissions, and internal processes makes
a big difference in keeping your Confluence installation secure. The following are
some tips you could consider. None of these make your installation a full 100 percent
secure, but they slow down or turn around any attacker.
In general you could say, "Don't put convenience go before security."
• Keep the number of Confluence administrators as low as possible, but having
just one is also not without risks.
• Restrict the number of users with powerful roles or group memberships. If
only one group of users should have access to some particular data, restrict
access to the data to those users. Do not give all staff access to sensitive data
when there is no need.
• Confluence administrators should have separate accounts for their
administrative role and for their day-to-day work.
