This seems entirely obvious and something a decent coder and ops team would protect against.
I guess the reason they are publishing a paper is so those who don't fall into the above category might actually realise how obvious and expensive this mistake can be.
Biting the hand that feeds IT
