Primula and BeSched

• As an employee, it is your responsibility to register your cases in Primula and BeSched, including those you've previously communicated to your manager during the systems' downtime.
• All data recorded until Friday, January 19, remains intact in the systems, so there's no need to re-enter that information.
• Refrain from registering cases that do not impact the February salary, such as planned absences occurring after February 29.

According to an update from TietoEvry, there is no indication that data has leaked in connection with the ransomware attack.

History

January 20 Our system provider, Tietoevry, was subjected to a ransomware attack, making it impossible to log in to Primula or BeSched. The integrations with other systems also stopped working. An internal security investigation was initiated. 

January 22 SLU reported to the Swedish Civil Contingencies Agency (MSB) regarding the information security incident, as the service disruption affects the accessibility of information in Primula and impacts our ability to carry out our mission. As a public authority, we are obligated by law to make this report. The January payroll was ensured. Preparations for handling the February payroll began.

January 23 SLU reported a personal data breach to the Swedish Authority for Privacy Protection (IMY). When personal data is inaccessible, it is considered a personal data breach, even if the information has not been further disseminated. As a public authority, we are obligated by law to make this report.

February 1 We regained access to Primula and started checking data and preparing to onboard employees and managers into the system.

February 6 Employees and managers were welcome to enter Primula again.

February 8 BeSched and the integrations with other systems were back in operation.