| ||||||
Steo 2: The policy should have key guidelines for component security, licensing and quality attributes. It should also cover guidelines that clearly lay out usage decisions like age of component at download, license-type, level of documentation. Step 3: These policies should not be in place just for the sake of it, instead it should be seriously followed. While it is easy to ignore paper-based policies, try to look for ways to integrate enforcement into the software development process itself. Step 4: Developers should have the power of information, else they will fail to make good choices and will face issues fighting back. If flaws are identified well in time, it can not only save time but also money. Step 5: If you know the inventory components and their dependencies before going into production, you will be able to carry out the troubleshooting easily and can even work on the vulnerabilities that may be discovered later. Step 6: It is important to keep an eye out for flaws that are discovered. New loopholes keep emerging and you have to keep an eye out for where it is being used exactly. Step 7: When faced with problems, have your plan in place. You should know how to fix the issue, irrespective of where it occurs. There can be last minute surprises by having a plan surely helps. |
menu bar
Monday, March 18, 2013
Steps To Secure Your Open Source Technology
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment