When configuring security for your JIRA instance, there are two areas to address:

• security within JIRA itself
• 外部環境内のセキュリティ

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:

1. Global permissions — these apply to JIRA as a whole (e.g. who can log in).
2. 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).
3. 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.
4. Comment visibility — allows the visibility of individual comments (within an issue) to be restricted.
5. Work-log visibility — allows the visibility of individual work-log entries (within an issue) to be restricted.

外部環境にセキュリティを設定する

JIRA インスタンスに機密情報が含まれている場合、JIRA インスタンスが起動する環境にセキュリティ設定をすることができます。以下に考慮事項を挙げます。

• データベース:
  • 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.)
• ファイルシステム — 以下のディレクトリへのアクセスは制限します (ただし、JIRA インスタンスを実行しているユーザーは、これらのディレクトリにフルアクセスします)。
  • インデックスディレクトリ
  • 添付ファイルディレクトリ
• SSL — if you are running your JIRA instance over the Internet, you may want to consider using SSL.

その他のセキュリティリソース

Security Addendum 2010-04-16 - Preventing security attacks