보안 버그 수정 정책
Atlassian에서는 제품의 취약점을 악용하여 고객 시스템에 손상이 발생하지 않도록 보장하는 것을 최우선으로 여깁니다.
범위
This policy describes how and when we may resolve security vulnerabilities in our products.
보안 버그 수정 SLO(서비스 수준 목표)
Atlassian sets service level objectives for fixing security vulnerabilities based on the security severity level and the affected product. We've defined the following timeframe objectives for fixing security issues in our products:
Accelerated Resolution Objectives
These timeframes apply to all cloud-based Atlassian products, and any other software or system that is managed by Atlassian, or is running on Atlassian infrastructure. They also apply to Jira Align (both the cloud and self-managed releases).
- Critical vulnerabilities to be fixed in product within 10 days of being verified
- High vulnerabilities to be fixed in product within 28 days of being verified
- Medium vulnerabilities to be fixed in product within 84 days of being verified
- Low vulnerabilities to be fixed in product within 175 days of being verified
연장된 해결 기간
These timeframe objectives apply to all self-managed Atlassian products. A self-managed product is installed by customers on customer-managed systems and includes Atlassian's Data Center and mobile apps.
- Critical, High, and Medium vulnerabilities to be fixed in product within 90 days of being verified
- Low vulnerabilities to be fixed in product within 180 days of being verified
중요 취약성
When a critical vulnerability is discovered by Atlassian or reported by a third party, Atlassian will take the following actions:
- For cloud products, we will ship a new fixed release for the affected product as soon as possible
- For self-managed products, we will:
- ship a bug fix release for the latest feature release of the affected product
- ship a new feature release for the affected product on the release schedule
- ship a bug fix release for all supported LTS releases of the affected product, in accordance with the Atlassian Support End of Life Policy.
제품 | 백 포트 정책 | 예 |
|---|---|---|
| Jira Software Server 및 Data Center Jira Core Server 및 Data Center Jira Service Management Server 및 Data Center(이전의 Jira Service Desk) | 다음에 대해 새로운 버그 수정 릴리스 배포:
| 예를 들어, 2020년 1월 1일에 중요 보안 버그 수정을 개발한 경우 다음과 같은 새로운 버그 수정 릴리스를 제작해야 합니다.
|
| Confluence Server 및 Data Center | 다음에 대해 새로운 버그 수정 릴리스 배포:
| 예를 들어, 2020년 1월 1일에 중요 보안 버그 수정을 개발한 경우 다음과 같은 새로운 버그 수정 릴리스를 제작해야 합니다.
|
| Bitbucket Server 및 Data Center | 다음에 대해 새로운 버그 수정 릴리스 배포:
| 예를 들어, 2020년 1월 1일에 중요 보안 버그 수정을 개발한 경우 다음과 같은 새로운 버그 수정 릴리스를 제작해야 합니다.
Bitbucket 6.3.0은 수정이 릴리스된 날보다 6개월 이상 앞선 2019년 5월 14일에 릴리스되었습니다. 이 릴리스는 장기 지원 릴리스로 지정되었으며, 버그 수정 릴리스도 제작됩니다. |
| Atlassian은 현재 및 이전 기능 릴리스 버전에 대한 새로운 버그 수정 릴리스만 배포합니다. | 예를 들어, 2020년 1월 1일에 Bamboo를 위한 중요 보안 버그 수정을 개발한 경우 다음과 같은 새로운 버그 수정 릴리스를 제작해야 합니다.
|
For Crowd, Fisheye, and Crucible, we will provide a bug fix release for the latest feature release of the affected product.
Examples of critical vulnerability fixes for self-managed products:
If a critical vulnerability fix is developed on Feb 1, 2024, the following are example releases that would receive the bug fix:
제품 | 예 |
|---|---|
| Jira Software | 예 Jira Software 9.13.x because 9.13.0 is the latest feature release |
| 예 Jira Software 9.12.x because 9.12.0 is the latest Long Term Support release | |
| 예 Jira Software 9.4.x because 9.4.0 is the previous Long Term Support release | |
| Jira Service Management | 예 Jira Service Management 5.13.x because 5.13.0 is the latest feature release |
| 예 Jira Service Management 5.12.x because 5.12.0 is the latest Long Term Support release | |
| 예 Jira Service Management 5.4.x because 5.4.0 is the second latest supported Long Term Support release | |
| Confluence | 예 Confluence 8.7.x because 8.7.0 is the latest feature release |
| 예 Confluence 8.5.x because 8.5.0 is the latest Long Term Support release | |
| 예 Confluence 7.19.x because 7.19.0 is the second latest supported Long Term Support release | |
| Bitbucket | 예 Bitbucket 8.17.x because 8.17.0 is the latest feature release |
| 예 Bitbucket 8.9.x because 8.9.0 is the latest Long Term Support release | |
| 예 Bitbucket 7.21.x because 7.21.0 is the second latest supported Long Term Support release | |
| Bamboo | 예 Bamboo 9.5.x because 9.5.0 is the latest feature release |
| 예 Bamboo 9.2.x because 9.2.0 is the latest Long Term Support release | |
| Crowd | 예 Crowd 5.3.x because 5.3.0 is the latest feature release |
| Fisheye/Crucible | 예 Fisheye/Crucible 4.8.x because 4.8.0 is the latest feature release |
No other product versions would receive new bug fixes.
Frequent upgrades ensure that your product instances are secure. It's a best practice to stay on the latest bug fix release of the latest feature release or LTS release of your product.
중요하지 않은 취약성
When a security issue of a High, Medium, or Low severity is discovered, Atlassian will aim to release a fix within the service level objectives listed at the beginning of this document. The fix may also be backported to Long Term Support releases, if feasible. The feasibility of backporting depends on complex dependencies, architectural changes, and compatibility, among other factors.
버그 수정 릴리스가 제공되면 설치를 업그레이드하여 최신 보안 수정을 적용해야 합니다.
기타 정보
The severity level of vulnerabilities is calculated based on Severity Levels for Security Issues.
We'll continuously evaluate our policies based on customer feedback and will provide any updates or changes on this page.