Security and data handling

This document outlines the security measures and data handling practices for portfolio insights. Portfolio insights adheres to Atlassian's security practices and complies with major data protection regulations, including GDPR and CCPA. For more information, see Atlassian Security Practices.

ポートフォリオ インサイトの以下のセクションでは、セキュリティの側面を取り上げています。

• Detecting Data Center and Cloud instances

• Connecting to Data Center instances

• Cloud readiness

• インスタンス最適化

• データ レジデンシー

Connecting to Data Center instances

To connect a Data Center instance, you install the Cloud Companion app, which creates a secure, outbound connection from your Data Center environment to Atlassian Cloud.

Cloud Companion の接続プロセス

To add an on-premises Data Center instance, install the cloud companion app to establish a secure link between your Data Center instance and Atlassian cloud.

セキュリティ キーの生成と使用

接続時に一意のセキュリティ キーが生成されます。

• The security key is valid for 180 days, after which you'll need to regenerate it to maintain the connection.

• 監査ログは組織レベルで入手でき、接続やアクションを追跡できます。

• クラウド側:

  • セキュリティ キーは不透明なトークンとして保存されます。

  • エンコードやデコードはできず、検証後にクラウドのセキュリティ サービスによってのみ承認されます。

  • トークンには個人を特定できる情報は含まれていません。

• オンプレミス側:

  • Stored at rest in your database, encrypted by default using AES/CBC/PKCS5Padding.

  • 暗号化キーは、製品の共有ホーム ディレクトリに安全に保存されます。

セキュリティ キーの送信

• セキュリティ キーは、リンク処理中に一度だけ表示されます。

• 管理ハブから手動でコピーして、Data Center インスタンスの [Linked Cloud Organization (リンクされた Cloud 組織)] セクションに貼り付ける必要があります。

• このプロセスにより、キーがログやシステム インターフェイスに表示されないようになります。

接続の暗号化

All data transmitted between your self-managed instance and Atlassian cloud is encrypted in transit using TLS 1.2+ with Perfect Forward Secrecy (PFS).

Detecting other Data Center instances

Portfolio insights detects your Atlassian Data Center instances in two ways: through license and domain information, and through existing app link connections.

ライセンスおよびドメインベースの検出

We use Atlassian’s license and billing systems to identify Data Center instances associated with your organization and verified domains:

• Scans license data stored in Atlassian’s license management system.

• ライセンス情報を、組織で申請されているドメインと照合します。

• Identifies Data Center instances associated with those verified domains.

During this process, we don’t store any personally identifiable information (PII). When contact information is needed, it’s fetched in real time from our license and identity systems and not stored by Portfolio insights.

アプリ リンクの検出

We rely only on app link metadata from your existing connections, not the app links or data behind them:

• Uses existing connections to retrieve app link metadata from your instance.

• Collects only non-sensitive metadata, such as URL, product family, server ID, and version.

Cloud readiness assessment for Data Center

This section describes what data we collect to create the cloud readiness assessment for your Data Center instances.

収集されるデータ

お客様のインスタンスを評価する際、次のデータを収集します。

• Jira or Confluence entities: Count and IDs of Jira or Confluence entities, such as projects and issues, spaces and pages, configuration entities. They’re retrieved directly from the database.

• Usage data: Metadata on the number of users and their activity around Jira or Confluence.

• Instance metadata: Metadata about your Jira or Confluence instance, such as hardware specification, network speed, and identifiers, like Server ID.

• ブラウザ指標: パフォーマンス指標に焦点を当てたユーザーとのやり取りのデータ。

• Marketplace app data: Count and IDs of entities coming from the most critical Marketplace apps.

For more detailed information on data points that we collect, see Assessing the scale of your Jira and Confluence instances.

特定可能なデータ

ユーザー名や課題キーなど、特定可能なデータは一切収集しません。すべて ID に基づいています。

課題のコンテンツや他のユーザーが作成したコンテンツ

ユーザーが作成したコンテンツのデータをスキャンまたは収集することはありません。

クラウド移行スコープ

Not all of the collected data is used in Portfolio insights. We collect raw data so it includes many more data points that we either plan to add to Portfolio insights in the future or make available to migration teams so they can understand your migration better and provide additional information if needed.

データの収集方法

When you connect to your instance, we run an assessment that on average takes up to a few hours, but should be much faster for less complex instances. Once it’s done, we’ll display the results in Portfolio insights:

データはどのくらいの期間クラウドに保存されますか？

Your data is stored in cloud for 2 years. Afterwards, it’s automatically deleted.

Instance health for Data Center

This section describes what data we collect for Instance health. You’ll also find details on how the data is transmitted and stored, and how it’s used to generate insights and recommendations.

データ収集

当社は、以下のデータを収集します。

1. Instance and node metadata: Product version, base URL, anonymized node identifiers, and Support Entitlement Number (SEN).

2. Performance metrics: JMX metrics on system performance (CPU load, database connection latency, garbage collection time, etc.).

3. Guardrails: Counts of performance-impacting entities (projects, users, groups, custom fields).

4. App usage data : Usage frequency of third-party, non-custom apps (collected by the App Usage for Jira app), Total REST API calls per app, Number of users actively using each app.

5. System behavior and configuration metrics: Anonymized information about system behavior including events (e.g. Jira reindex) and metrics (e.g. counts of issues, configuration).

For a detailed view of the data we collect, refer to our assessments file 

• Jira instance_optimization_metrics.json

• Confluence instance_optimization_metrics.json

These files provides a structured representation of performance metrics and guardrails data.

各メトリック エントリには以下が含まれます。

• メトリック名: 追跡対象の特定のメトリック。

• 属性: パフォーマンス指標の値など、メトリックのデータを表すキーと値のペア。

• Type: The category of the metric, such as JMX_METRIC for performance metrics or GUARDRAILS for counts, APP_USAGEfor apps usage information, SYSTEM_EVENT or  SYSTEM_METRIC for behavioural information

• タイムスタンプ: メトリックが記録された日時。

• Tags: Additional metric information necessary to provide valuable recommendations (pluginKey for public or Atlassian-owned apps for which the metric is generated).

収集プロセス

• The ATST (Atlassian Troubleshooting and Support Tools) plugin collects metrics every 2 minutes.

• データは 1 時間ごとに集計され、Atlassian Cloud に送信されます。

• ガードレール データは 1 時間ごとに収集されます。

データ ストレージ

• Performance data is securely stored in Atlassian Cloud for 2 years, then automatically deleted.

• ストレージにより、過去の傾向分析とパフォーマンスの比較が可能になります。

データ転送とセキュリティ

• All data is encrypted in transit using TLS 1.2+ with Perfect Forward Secrecy (PFS).

• セキュアなトークンが、Atlassian Cloud に送信されたデータを認証します。

• We don’t transfer any PII or user-generated content automatically to Atlassian Cloud for connected instances. However, if you manually upload the support.zip file, it may include this data as described below.

データの使用

収集されたデータは次の目的で使用されます。

• 最適化スコアを計算する。

• 詳細なパフォーマンス インサイトを提供する。

• 実用的な推奨事項を生成する。

• 時間の経過に伴うパフォーマンス トレンドを特定する。

Manual upload of support.zip

If you’re unable to connect your Data Center instance, you can manually create the support.zip file and upload it to Portfolio insights. We’ll use the results from this file to show Optimization insights.

Important information:

• Before you create the support.zip, you need to update the Atlassian Troubleshooting and Support Tools (ATST) app to the latest version.

• The support.zip may contain personal information such as usernames, email addresses, and IP addresses that are recorded in the logs and diagnostic data. This it a limitation of using the support.zip and doesn’t apply when you connect your instance to Portfolio insights.

For more info, see Collect and upload Instance health data manually.

プライバシーとコンプライアンス

• アトラシアンのセキュリティ慣行に準拠しています。

• GDPR、CCPA、およびその他の主要なデータ保護規制に準拠しています。

データ レジデンシー

You can control the location of the data that we collect and use in Portfolio insights.

Change the location

To change the location of your data:

1. Go to admin.atlassian.com, and select your organization.

2. Select Insights > Portfolio insights.

3. Select either Cloud readiness or Instance health. The change will apply to data from both of these features.

4. In the top right, select … > Manage data residency.

5. Select Change location via request. You’ll be moved to a portal where you can fill out the request details, including your information and a new location.

6. Select Submit to send the request.

When submitted, the Portfolio insights team will review your request and prepare to move the data. Once we start moving the data, Portfolio insights won’t be available – this might take up to a few hours.

Additional change for manual upload of support.zip

The manual upload of support.zip file used for Optimization insights has separate controls for data residency. If you used this manual upload, you need to make an additional data residency change.

To change data residency for support.zip:

1. Go to admin.atlassian.com, and select your organization.

2. Go to Data management > Data residency.

3. Set a new location.

Data stored and the default location

By default, the Portfolio insights data is stored in the Global location.

The data we store is specific to your usage of Portfolio insights, and includes data or metadata related to the following capabilities:

• Detecting Data Center instances

• Connecting to Data Center instances

• Data collected and used for Instance health for Data Center

• Data collected and used for Cloud readiness for Data Center

The details of what we collect are described on the page you’re viewing, please review it for more information.

Portfolio insights doesn’t include any in-scope data from any of your instances, such as content of issues or pages, or details of users.

Available locations

Each location corresponds with one or more AWS regions, which are physical locations around the world where AWS clusters its data centers. Learn more about AWS infrastructure and its role in our cloud hosting infrastructure.

By default, your data is hosted in the Global location, which includes all of our AWS regions. This means that we might move data between AWS regions if needed for performance or other reasons.