SaaS Security Administrator's Guide
    : Begin Scanning a Jira App
    Focus
    Download PDF
    Focus
    1. Home
    2. SaaS Security
    3. SaaS Security Administrator's Guide
    4. Data Security
    5. Secure Sanctioned SaaS Apps on Data Security
    6. Add Cloud Apps to Data Security
    7. Begin Scanning a Jira App
    Download PDF

    SaaS Security Administrator's Guide

    Begin Scanning a Jira App

    Table of Contents

    Begin Scanning a Jira App

    Authorize Data Security to connect to Jira to scan all content shared within the app.
    To connect a Jira app and begin scanning assets, you need to:
    • Ensure that you have a Jira Administrator account with workspace-level permissions.
    • Grant Data Security access to Jira Cloud.
    • Add the Jira app to Data Security, providing Data Security information about your Jira Cloud account.
    If you onboarded your Jira app before June 30, 2022, there is a newly published app available on the Jira Marketplace. To replace your existing app, you must delete and reonboard the app. If you don’t, some new features won't be available, including remediation and user activity monitoring capabilities. Your existing app does not support remediation, so you likely did not create any policy rules that are purged when you delete the app. After reonboarding, you can create policy rules for improved data loss prevention.
    Support for automated remediation capabilities varies by SaaS application.

    Add Jira App

    In order for Data Security to scan assets, you must consent to specific permissions during adding the Jira app.
    1. (Recommended) Add your Jira domain as an internal domain.
    2. Log on to SaaS Security.
    3. To add the Jira app, go to Data SecurityApplicationsAdd ApplicationJira.
    4. Sign in to the Atlassian workspace with an account that has workspace-level Administrator permissions.
    5. Follow the onscreen instructions in Step 1: Specify your team’s Atlassian workspace URL.
    6. Follow the onscreen instructions in Step 2: Go to Atlassian Marketplace, and Enable Private Listings on Manage apps.
      Data Security isn't currently available publicly on the Jira Marketplace, so this temporary step is needed to initiate the installation. If you don't perform this step the Upload app button outlined in the next step does not display.
    7. Follow the onscreen instructions in Step 3:
      1. Copy the URL, and paste it in Manage appsUpload app.
      2. Authorize for your workspace, then Accept the requested access.
        Data Security requires this access to scan your assets on Jira.
      3. Click Complete Jira Installation.
        Data Security adds the new Jira app to the list of Cloud Apps as Jira n, where n is the number of Jira app instances that you have connected to Data Security. You’ll specify a descriptive name soon.

    Customize Jira App

    After you add the Jira app, customize the app to make use of capabilities that are unique to this app or that differentiate this app instance from others.
    1. (Optional) Give a descriptive name to this app instance.
      1. Select the Jiran link on the Cloud Apps list.
      2. Enter a descriptive Name to differentiate this instance of Jira from other instances.
      3. Click Done to save your changes.
    2. Next step: Proceed to Identify Risks.

    Identify Risks

    When you add a new cloud app, then enable scanning, Data Security automatically scans the cloud app against the default data patterns and displays the match occurrences. You can take action now to improve your scan results and identify risks.
    1. To start scanning the new Jira app for incidents, go to Data SecurityApplicationsJiraEnable Scanning.
    2. Monitor the scan results.
      During the discovery phase, as Data Security scans files and matches them against enabled policy rules:
      • Verify that Data Security displays assets.
      • Verify that your default policy rules are effective. If the results don’t capture all the risks or you see false positives, proceed to the next step to improve your results.
    3. (Optional) Modify match criteria for existing policy rules.
    4. (Optional) Add new policy rules.
      Consider the business use of your cloud app, then identify risks unique to your enterprise. As necessary, add new:
    5. (Optional) Configure or edit a data pattern.
      You can Configure Data Patterns to identify specific strings of text, characters, words, or patterns to make it possible to find all instances of text that match a data pattern you specify.
    6. Next step: Proceed to Fix Jira App Onboarding and Scan Issues, if necessary.

    Fix Jira App Onboarding and Scan Issues

    The most common issues related to onboarding a Jira app are as follows:
    Symptom
    Explanation
    Solution
    Attachments embedded in comments don’t display in SaaS Security web interface.
    Attachments embedded inside descriptions or comments are not currently supported—only attachments added through the attach button are scanned for violations.
    This is expected behavior. However, periodically monitor the support because new support is added regularly.
    Attachments embedded in descriptions don’t display in SaaS Security web interface.
    Primary Email of the asset owner related to Jira app doesn’t display in the SaaS Security web interface.
    Sometimes users explicitly block outsiders (apps or people) from viewing their contact information, which includes email address.
    Set Contact Email address to Anyone to display this information.
    From Profile and visibility, navigate to ContactEmail addressWho can see this? and enable Anyone.
    Deletions don’t display in the SaaS Security web interface as expected.
    Delete event is supported for permanent deletion.
    Jira empties the Trash automatically after 60 days or administrators can permanently delete what’s in Trash.
    This is expected behavior. Wait 60 days or empty the Trash manually.
    Comments for user activity and events display in the SaaS Security web interface, but one comment appears to be a duplicate of another as the Target Name for each is the same.
    All comments have a unique Target Name. However, the SaaS Security web interface only displays the first 16 characters for optimal viewing as some names can be quite long.
    This is expected behavior and by design.
    Supported remediation and user activity monitoring capabilities don’t seem to be available on my tenant.
    If you onboarded your Jira app before June 30, 2022, 2022, you have an outdated version of the app.
    To replace it with the newly published app available on the Jira Marketplace, you must delete and reonboard the app.

    FAQs for Jira App

    The most common questions related to onboarding a Jira app are as follows:
    Question
    Answer
    What are the different events or activities supported for Jira app?
    Create and delete of issues, projects, comments, and attachments.
    Delete is defined as permanently deletion. See Fix Jira App Onboarding and Scan Issues.
    How are Issue description violations named?
    They are named using the format Issue: {issue-key}.
    How are Issue comment violations named?
    They are named using the format `Comment: {issue-key}.
    How are Issue attachment violations named?
    They are named using the format `Attachment: {attachment-name}.
    How do I search for all assets related to a Jira Issue?
    You can retrieve assets as follows:
    • Description violations and comment violations—Type the Issue-Key
    • Attachment violations—Search by attachment name or by application name.

    © 2024 Palo Alto Networks, Inc. All rights reserved.