Caught off-guard with sensitive data? Stay on-guard with Guard Premium + Automation for Confluence

[#1]

Hi Atlassian Community, 

The Guard Premium team is ecstatic to introduce a new dynamic duo: Confluence automation and Atlassian Guard Premium content scanning. Swiftly respond when sensitive data is identified, available now!

Managing sensitive data has become even more crucial as the volume of data generated and processed daily continues to grow. Embracing automation saves valuable time and minimizes the risk of human error, ultimately protecting your data and maintaining the trust of your users.

Guard Detect generates an alert whenever a Confluence page is modified and contains specific types of sensitive data, such as credentials, financial information, or identity details.

Now, you can harness the potential of Confluence automations to respond when sensitive data is found. You have the option to create your own rule using the new Content scanning alert trigger or explore pre-existing templates to kickstart your process.

Curious about how automations can streamline your sensitive data response? Here are some ideas:

• Classify the page containing sensitive data.

• Restrict access to the page and provide guidance through a comment or email regarding your company's sensitive data policy.

• Create a Jira ticket to outline the necessary steps for data cleanup.

You can customize the trigger to run the rule for any content scanning alert, or only for specific alerts like API keys or credit card numbers. With Confluence automation's wide array of actions and conditions, the possibilities are endless.

Content scanning alerts are available with Atlassian Guard Premium. Automation is available with a Confluence Premium or Enterprise plan.

Where to begin?

The quickest way to begin is to use a template:

1. Navigate to Automations within Confluence.

2. Select the Templates tab.

3. Choose the Respond to security alerts category.

4. Select a template and follow the prompts to configure it.

We recommend initially creating a rule in a test space. Once you're happy with the rule, you can set up a global rule. If you have multiple Confluence instances, remember that each instance will need its own rule configuration.

Read more about how automation works with Guard Detect

What's on the horizon?

We are constantly working on new ways to enhance your ability to respond to security incidents more efficiently. Our next area of focus involves automating user activity detections, giving you the power to quickly respond to any unusual behavior within your organization. Additionally, we are broadening the features for automatic responses when sensitive data is detected. Keep an eye out for further updates!

We believe these improvements will help you better handle sensitive data within your organization. Your feedback means a lot to us, and we're here to support you through it all.

Cheers,

The Atlassian Guard Premium Team

[Tomislav Tobijas _Koios_]

This could actually be really useful when it comes to DORA regulation and some best practices for enhancing security. 🛡️

Thanks for sharing!

[Magic Mike]

It's very common to see companies having pages containing sensible information like logins/passwords or IP addresses, even if those are not production credentials, often the test environnement can also contain real data. This is one of the first thing I check when auditing Jira and Confluence.

☝️This is a game changer ! Thanks @Audrey Garcia