This is good on the face of it, but there must be a tiered secure way for Australian techs can access and learn how to use and implement.
One like to think that Australia, as one of the 'five eyes' has this down pat, but I have read of stories where low level data stores of unimportant stuff are maintained on servers that also hold several other tiers of data up to top secret, and data can be moved laterally, bypassing the security needed. Cloud storage can and has been penetrated, often in a way that does not reveal the loss.
So what is needed in a 'vaults within vaults method, like the
matryoshkas dolls are nested. Each time you open a doll, the security differs, the encryption differs etc etc, so a hacker can not go 1-2-3-4 through all the levels.
They also need 'canaries'. (canaries - the small birds, are exquisitely sensitive to poisonous mine gasses and miners would take down a small cage with a canary in it. The bird would stop chirping, fall off the perch or even die far quicker than a human, so they watched the canary - anything happens, get out now).
In data stores, the canary would be a complex set of files that used the nomenclature of the target company, file names, project names, people etc. The contents would be well encrypted, but would have no valid data, just stuff deeply encrypted so the crooks think they found 30 gigs of data, movies etc - they would grab and decode later. This would give the impression of a hacking job well done. Of course, the canary implementation scripts collect whatever data they can, pings, IP numbers - all the baggage they can get. The canary would 'lose the connection' from time to time, to see how/where it is reconnects.
If all goes well, they only get canary guts to eat - if not, they may get data. This would be deeply encrypted, so the true data in there can not be winkled out.
This is serious business. You can bet Russia, China, Korea make it hard to steal their data, so the 5 eyes need to be even better. https://en.wikipedia.org/wiki/Five_Eyes
1 comment
[ 3.0 ms ] story [ 10.8 ms ] thread