31–40 of 207 posts
Rule #1 about databases: It will be hacked. Rule #2: see rule #1
That would imply that security is irrelevant. Maybe you should re-work your rule the say that it will attempt to be hacked. Therefore you should always worry about security.
Rule #1 about databases: It will be hacked. Rule #2: see rule #1
That would imply that security is irrelevant. Maybe you should re-work your rule the say that it will attempt to be hacked. Therefore you should always worry about security.
> On May 31, 2019, CBP learned that a subcontractor, in violation of CBP policies and without CBP’s authorization or knowledge, had transferred copies of license plate images and traveler images collected by CBP to the subcontractor’s company network > CBP ... is closely monitoring all CBP work by the subcontractor What. In the private sector, they'd have been fired and probably legal action levelled against them. Th…
Remember the time Experian got hacked and the CEO subsequently retired with a $90M payday? The private sector is just as consequence-free.
Rule #1 about databases: It will be hacked. Rule #2: see rule #1
That would imply that security is irrelevant. Maybe you should re-work your rule the say that it will attempt to be hacked. Therefore you should always worry about security.
> On May 31, 2019, CBP learned that a subcontractor, in violation of CBP policies and without CBP’s authorization or knowledge, had transferred copies of license plate images and traveler images collected by CBP to the subcontractor’s company network > CBP ... is closely monitoring all CBP work by the subcontractor What. In the private sector, they'd have been fired and probably legal action levelled against them. Th…
(In the enterprise software world, I can tell you how epic failure to perform on an 8+ figure contract unfolds: the sales guy takes a VP out to the next game so they can discuss it over drinks in the corporate box and nothing will change)
Earlier quoted context omitted.
Remember the time Experian got hacked and the CEO subsequently retired with a $90M payday? The private sector is just as consequence-free.
Only politically connected companies, if you and I ran a business like that the outcome would have been different. The state has no problem going after small businesses.
> On May 31, 2019, CBP learned that a subcontractor, in violation of CBP policies and without CBP’s authorization or knowledge, had transferred copies of license plate images and traveler images collected by CBP to the subcontractor’s company network > CBP ... is closely monitoring all CBP work by the subcontractor What. In the private sector, they'd have been fired and probably legal action levelled against them. Th…
Tell me again one meaningful action against a data leak in the private sector. I'll wait.
Earlier quoted context omitted.
anyone ? Why is a 3rd party given the ability to store such a large database to conduct such business ? They should at most store the last 3 months border documents, nothing older than this.
I _think_ OP was trying to be sarcastic.
Rule #1 about databases: It will be hacked. Rule #2: see rule #1
That would imply that security is irrelevant. Maybe you should re-work your rule the say that it will attempt to be hacked. Therefore you should always worry about security.
This implies that in addition to reducing the likelihood of breaches, you should also focus on all the other aspects of security, especially detection and mitigation; and for databases one of the main ways of reducing the impact of breaches is to avoid storing sensitive information as much as possible. In this particular example, was it really necessary to store pictures of license plates beyond a very limited period of time? A breach can't leak what you don't store, and you will get some breaches.
https://www.washingtonpost.com/technology/2019/06/10/your-fa...