Comprehensive software reviews to make better IT decisions
Zendesk Data Breach – How Am I Affected?
Zendesk experienced a data breach of 10,000 accounts. Users of Zendesk Support and Zendesk Chat whose accounts were activated prior to November 1, 2016, were affected.
According to Zendesk’s blog, unauthorized access to Zendesk customer information may have included:
- Agent and end-user names and contact information
- Usernames and hashed and salted passwords
- Transport Layer Security (TLS) certificates provided to Zendesk by customers
- App marketplace settings, including a small number of integration keys or passwords used by Zendesk apps to authenticate against third-party services
Source: Zendesk, Updated Notice Regarding 2016 Security Incident
The customer contact information may pose a breach of personal privacy, invoking privacy legislation depending on jurisdiction.
Although passwords were hashed and salted, the disclosure of usernames may enable the use and increase success of brute-force attack on the known usernames.
The SSL certificate theft may be of concern. Transport Layer Security uses SSL certificates to enable secure site-to-site communications without the means of a dedicated circuit or VPN Tunnel. Today, SSL certificate validity periods are limited to up to two years, however, in 2016, SSL certificates of up to three years were available. And so, it is theoretically possible that a number of 2016 certificates are still in use, although three months still remain of 2019. This may be of concern to some organizations who are using such certificates in their Zendesk configuration. We recommend that Zendesk customers check their SSL certificate validity dates as soon as possible.
The integration keys and passwords may pose a security vulnerability to some organizations, particularly if those passwords have remained static since 2016. We recommend that Zendesk integration passwords are changed on a regular basis.
No one can predict when their service provider will get hacked and when their data will become exposed, but a number of precautions may help reduce risk and exposure on an on-going basis on any service, on-premises or cloud-based:
- Change your passwords regularly. These include any passwords related to integration accounts or operating system service accounts.
- Security certificates (also known as HTTPS or SSL certificates) should be set to expire/renew more frequently, possibly on an annual basis. Although the current industry Certificate Authority/Browser Forum (“CAB Forum”) specifies a maximum of 27 months, shorter timeframes to ensure that the credentials “renew” more frequently will help mitigate the risks described in this article. Note: It is imperative that you remember to renew the certificates within 30 days of their expiry!
- Review your data governance rules around what information can be stored on which cloud service. Conceivably, some cloud-based systems will require you to store highly confidential data (such as HRIS system storing employee data), however, if you can limit the type of information that is stored on a cloud service (say, nothing confidential on a cloud ITSM system), that will help mitigate privacy concerns around data breaches.
Want to Know More?Identify the Best Framework for Your Security Policies
Thinking about choosing a new software vendor but don't know where to start? Narrow down your shortlist by focusing on software that has received an Info-Tech Research Group award. New data from SoftwareReviews shows that organizations reported higher satisfaction when they switched to software that had received an Info-Tech award.
Atlassian has acquired Halp, a real-time helpdesk tool that integrates with Slack. With the broader context of this move being Atlassian and Slack’s strategic alliance, might there be more to this acquisition than meets the eye?
Organizations are complex and have multiple stakeholders involved in the delivery of a service. In a public sector organization, for example, there are end users, multiple agencies and departments, and vendors involved in the delivery and consumption of the service. Service design methods and tools assist in making sense of these stakeholders’ inter-relationships and allow organizations to make sound decisions during service implementation.
The impact of COVID-19, as it became a global pandemic in Q1 of 2020, has affected user sentiment toward software during a growing period of fear, uncertainty, and doubt. To analyze the impact, SoftwareReviews compared Satisfaction (willingness to recommend to a peer), ability to deliver Business Value (fair cost to value), and Likeliness to Renew prior to March 10 and post March 10.
ITSM vendor InvGate announced that due to COVID-19 any organization can use InvGate Service Desk free of charge. This promotion helps IT departments when they need it most while gaining adoption and market traction for InvGate.
ServiceNow’s Orlando release introduced Now Intelligence, a set of features that strengthen ServiceNow’s lead in the AI-powered IT service management (ITSM) and digital transformation space.
Ivanti is well positioned to build on a solid ITSM foundation and will deliver expanded capability in areas such as mobility, customer experience, enterprise service management, and artificial intelligence.
IT solutions provider BMC announced that Shared Services Canada (SSC) has selected BMC Remedy to be its new ITSM platform. This adoption shows that BMC continues to be a viable option for governments and large enterprises.
ServiceNow has released four free emergency response apps to help customers with crisis management in the wake of COVID-19, including emergence response operations, employee outreach, self-reporting, and exposure management.