Threat-Centric Thinking on the Rise
While reading it, it struck me that while you do a very good job covering "who" and "how" nothing was said about "why". who/how/why form audit trial, and all are required to make the records useful.
In this context, "how" is a technical issue, "who" is interesting to the enforcers (lawyers/HR/Marines), and management needs to know "why".
In general, once I know what the threat is I can remove it (process or force), remove the opportunity (how will you do it?) for the threat to cause damage, or I can remove the incentive (why do it?) the threat has to take whatever action hurts me.
Forcibly removing threats is illegal, and in many cases legal action is not possible (what jurisdiction is N Korea again?), or it can be less than cost-efficient.
Most companies try to do their best to remove the opportunities by controlling their security posture.
Removing the incentives can be done by making yourself less interesting than other targets, or by not having what the attacker seeks. If I know who targets me, be it helpdesk employees or the students from the Philippines, I can try to discover what they seek, and remove the item or put it behind access controls that will make it less interesting.
In general, you are right - while secrecy is a staple of security, safety of the Internet requires open cooperation.
Thanks for the comment. If the incentive is the blueprints to the very thing that your company makes, you can't really remove the incentive. You can only increase the cost/risk to the attacker.
If I missed your point, lemme know.
Cheers!
Firewalls/IDS/IdM/etc are piled on top of the wire connection, because connectivity brings more worth than it costs in the losses.
Removing incentives works best, because it deals with the issue before even the perpetrator is created. It's hardly possible to recommend this approach as the base for your security posture, but it will help in the long term. The very nature of security is that risk is controlled by a circle formed of checks and balances, which together are supposed to bring the cost of security down to an acceptable level.
To give you a concrete example, I am trying to complete support for rewriting our 3rd party connection agreement in a way that will make our control over the partner (vendors/contractors/etc) connection much better. It will not add any more access controls but, if I am successful, the end result will be that the non-employees will be less likely to ignore the policy that governs their access. It's done by improving the contract language, improving their ability to request additional access, and our ability to audit their access. In the end we run the same firesieve, but fitted with a finer mesh.
Can someone sneak by and do something bad? Sure. It's the same technology, the same rules will apply to their access.
Will I be in much better position to detect it, and to prosecute them? Sure. Better provisioning allows us to create and disable accounts easier, which limits the number of group accounts, which increases accountability, which raises our change to even consider recovering damages, which makes the 3rd party pay more attention (hopefully) in order to limit their losses, which should result in better processes on their end, and make them notifying us when, for example, they fire someone, much much quicker, etc, etc. It's a process that, when the number of external entities is multiplied by the amount of work they do, gives a very good chance of being worth the time and effort that it requires.
Cost? Internal labor and skill, which are in high demand, which makes me work really hard to state and defend the case for this project :-)