When configuring security for your JIRA instance, there are two areas to address:
- security within JIRA itself
- security in the external environment
Configuring security within JIRA
JIRA has a flexible security system which allows you to configure who can access JIRA, and what they can do/see within JIRA.
There are five types of security within JIRA:
- Global permissions — these apply to JIRA as a whole (e.g. who can log in).
- Project permissions — organised into permission schemes, these apply to projects as a whole (e.g. who can see the project's issues ('Browse' permission), create, edit and assign them).
- Issue security levels — organised into security schemes, these allow the visibility of individual issues to be adjusted, within the bounds of the project's permissions.
- Comment visibility — allows the visibility of individual comments (within an issue) to be restricted.
- Work-log visibility — allows the visibility of individual work-log entries (within an issue) to be restricted.
Configuring security in the external environment
If your JIRA instance contains sensitive information, you may want to configure security in the environment in which your JIRA instance is running. Some of the main areas to consider are:
- If you are using an external database as recommended for production systems (i.e. you are not using the HSQL database that is bundled with JIRA Standalone), you should restrict access to the database that your JIRA instance uses.
- If you are using the embedded HSQL database that is bundled with JIRA Standalone, you should restrict access to the directory in which you installed JIRA. (Note that the user which your JIRA instance is running as will require full access to this directory.)
- File system — you should restrict access to the following directories (but note that the user which your JIRA instance is running as will require full access to these directories):
- SSL — if you are running your JIRA instance over the Internet, you may want to consider using SSL.