View source for White paper: Reduce your open source security risk

It’s incumbent on developers, project team leaders, IT managers, CIOs, line of business owners, all the way up to C-level executives to ensure that there are sound strategies and tactics in place to make it easy to acquire, distribute, use, monitor, analyze, and keep track of open source software to reduce the risk of vulnerable and buggy software and applications to an absolute minimum.

So, this white paper presented how to employ new strategies, tactics and tools to reduce their open source security risk.

== White Paper main segments ==
This is the main segments of this white paper:
* The challenges facing open source developers
* List of a few questions to assess potential risk and liabilities.
* Straightforward tactics that significantly reduce OSS risks:
# Create OSS policies
# Create an OSS acquisition process
# Managing provisioning
# Tracking usage
  # Ongoing monitoring and analysing

== Conclusion == 
Open source software is here to stay but that doesn't mean that developers can use it without considering the vulnerabilities and security issues they may introduce into their development projects. The fact is, there’s no such thing as bulletproof, bug-free, automatically license compliant, and easily auditable software. Not in the open source world and not in the commercial off the shelf (COTS) world.

== Full White Paper ==
[http://www.roguewave.com/getattachment/86b39f44-d425-4bd5-94a8-3ab4f18d4882/Reduce-OSS-risk-Strategies-tools-tactics?sitename=RogueWave Reduce your open source security risk: Strategies, tactics, and tools - by RogeWave company]