“It took us some time before we could trace it to a firewall issue. It was not one in all the apparent causes to have a look at,” Strachan Stine Smemo, the Bane external communications manager, said in an email to Computerworld. “It was tricky to search out the issue.”
Bane’s team opted against changing any firewall settings and as an alternative — as a short lived measure — switched communications to a special firewall. (They later modified the impacted components, Smemo said.)
Arild Nybrodahl, Bane’s information and communications technology director, said his team detected “system instability” on Christmas Eve, which is when “troubleshooting efforts were initiated.” Things didn’t get bad enough to shutdown operations until 8 a.m. the subsequent day, he said.
