The ECB is the governing body for cricket in England and Wales and was founded in 1997. Based in Lords the ECB is owned by 41 members, comprising 18 1st Class counties and 21 non-1st Class, that’s 39 counties in all. The ECB is responsible for the professional game of cricket which includes safe guarding, managing players, tournaments and events – they also run a leading-edge performance centre, at Loughborough where they share resources with the university. The ECB also looks after the recreational game, governing around 6,000 clubs in England, Wales and Scotland and nurture grass roots for the game which includes creating the All Stars and recent Dynamos program to
ignite and increase participation of young players, both boys, and girls.
England & Wales Cricket Board
BACKGROUND
The ECB embraced cloud computing and hosting services a few years ago, which included moving to Office 365 and SharePoint. The transition was completed towards the end of 2019, and this allowed them to move seamlessly over to the new way of remote working when COVID hit.
What sensitive data does the ECB deal with?
The ECB works with a very dispersed number of organisations, with people working all over the UK. Then there’s the partner organisations in both the UK and around the world. They deal with large volumes of sensitive information pertaining to players, organisers, communities, sponsors, and other
stakeholders.
Keeping control of “Who has access to what”
The ECB’s information of state and who needs access to what information is complex and difficult to track. Whilst they have a plethora of security layers in place, this doesn’t take away the fact that, when it comes to securing data, people are the weakest link.
IMPLEMENTATION
“When I first saw Torsion, I was very impressed not only by its capabilities but also by how intuitive it appeared appear to be, and easily integrated with SharePoint and OneDrive.
“We agreed the project plan and started by applying the ownership and certification feature, which allows us to see who has access to what and provide the reporting to site owners and IT. The next step was to connect the Torsion system to our Office365 and that was very straight forward. We decided to roll the platform out to three departments initially so we ran a requirements workshop so we could capture and understand the business information that was needed. The Torsion solution was then configured for the three teams and user comms distributed to all the team members. We then switched Torsion on, and a sharing and security menu item seamlessly appeared within Sharepoint.
“Torsion also leaves the native sharing tools there, however, so if users still wish to use those they can. It’s perfect for us.”