Atlassian CSIRT team enquiry

[Jason Steer]

Hi, my employer is a customer of Jira.

We are mapping suppliers with key contacts in case of critical events. 

Does Atlassian have a security/CSIRT group where we can reachout to in case of a critical event ?

thanks

jason

[Dirk Ronsmans · Accepted solution]

Hi @Jason Steer and welcome to the community!

Could you clarify what type of Critical event this would be?

If you require support for a high priority issue or event you'll have to create a P1 ticket at https://support.atlassian.com/contact

Unless you have a TAM (Technical Account Manager) assigned to you based on your contract, but normally if you have one of those you'll be paying for it and I would assume you know the person :)

[Jason Steer]

thank you @Dirk Ronsmans - that was quick!

Sorry the fluffy description - it would be an event (theoretical) such as a ransomware attack on Atlassian that impacted many/all Atlassian clients.

Would and could we raise a ticket  if your system were down or impacted to the point that we would need another way to reach to you for guidance?

Does that make sense?

thank you

jason    

[Dirk Ronsmans]

Hi @Jason Steer ,

Let me first clarify that we are just volunteers and not Atlassian employees so my feedback is based on public documentation and my experience :)

I would hope that if such a massive event occurs that Atlassian is aware immediately themselves too. There is also the statuspage that exists (https://status.atlassian.com)

The support system should be separate from the customer instances imho..

Just for good measure I'll try and loop in the Atlassian engineers and have someone chime in on this from their end :)

I would also look in to the TAM concept if you really need a "direct" line

https://www.atlassian.com/enterprise/tam

[Jason Steer]

thank you @Dirk Ronsmans - much appreciated for your help. 

I've been trying (and failing) to get to this level of detail and as yet have not been able to find out any more. 

I will ask some further questions on TAM internally. 

thanks again :)

jason