Last updated:
30th December 2024
See answers to previous information requests
How to search
- Select a year and/or a month from the drop down list
- Type a subject into the 'Subject keyword(s):' search (Optional)
- Click 'Search' button
Alternatively click 'View' to browse through all received requests.
This search is for our information requests from September 2020 onward.
Cyber security breaches
See notes
I would like to request the following information for each calendar year from 2020 to 2026 inclusive:
1. The number of cyber security breaches that have being identified that were found to be a result of a malicious threat actor (i.e. not accidental data breach)
a) 2020:
b) 2021:
c) 2022:
d) 2023:
e) 2024:
f) 2025:
g) 2026:
2. The breakdown in high-level causes of these breaches as identified by cyber security incident response teams (CSIRTs), for example (but not limited to) unpatched software/hardware, lack of multi-factor authentication (MFA), leaked user credentials, lack of in-transit encryption, etc
a) 2020:
b) 2021:
c) 2022:
d) 2023:
e) 2024:
f) 2025:
g) 2026:
3. The number of breaches that occurred that were attributed to a previously known vulnerability to the organisations hardware, software, policies, or processes, for example where system was known to be at risk due to being unpatched or out of support, or security controls were recommended but not enforced, and was defined within the resulting incident response report.
a) 2020:
b) 2021:
c) 2022:
d) 2023:
e) 2024:
f) 2025:
g) 2026:
4. The estimated combined costs incurred as a result of cyber security breaches defined in request number one in each year.
a) 2020:
b) 2021:
c) 2022:
d) 2023:
e) 2024:
f) 2025:
g) 2026:
I would like to request the following information for each calendar year from 2020 to 2026 inclusive:
1. The number of cyber security breaches that have being identified that were found to be a result of a malicious threat actor (i.e. not accidental data breach)
a) 2020:
b) 2021:
c) 2022:
d) 2023:
e) 2024:
f) 2025:
g) 2026:
Wokingham Borough Council have not had any cyber security breaches
2. The breakdown in high-level causes of these breaches as identified by cyber security incident response teams (CSIRTs), for example (but not limited to) unpatched software/hardware, lack of multi-factor authentication (MFA), leaked user credentials, lack of in-transit encryption, etc
a) 2020:
b) 2021:
c) 2022:
d) 2023:
e) 2024:
f) 2025:
g) 2026:
Wokingham Borough Council have not had any cyber security breaches
3. The number of breaches that occurred that were attributed to a previously known vulnerability to the organisations hardware, software, policies, or processes, for example where system was known to be at risk due to being unpatched or out of support, or security controls were recommended but not enforced, and was defined within the resulting incident response report.
a) 2020:
b) 2021:
c) 2022:
d) 2023:
e) 2024:
f) 2025:
g) 2026:
Wokingham Borough Council have not had any cyber security breaches
4. The estimated combined costs incurred as a result of cyber security breaches defined in request number one in each year.
a) 2020:
b) 2021:
c) 2022:
d) 2023:
e) 2024:
f) 2025:
g) 2026:
Wokingham Borough Council have not had any cyber security breaches
