Learn How to Integrate Your Security Policies into TeamMentor

Posted by Tom Bain on November 16, 2011 at 9:59 AM

TeamMentor is the industry's only knowledgebase for secure software guidance. We’re launching TeamMentor this month, along with a new demo series so that you can see this product in action.

It's only so often that a tool like this comes around that is a not just a tool, but a full solution for secure software development for developers and security teams. We’ve created this demo program so that you can understand exactly how to use the TeamMentor.

With TeamMentor, development and security teams are able to finally able to fully integrate security into the software development process as TeamMentor was built to specifically map to secure development lifecycle best practices.

For example, if you are managing or part of a team that is working on a specific software project, you’ll likely have to troubleshoot some issues. Two common issues you might encounter are potential vulnerabilities in the code you are creating, and how to quickly resolve that issue and get back to developing.

So let’s say you do some initial testing and the issue comes down a piece of code that is linked to a known cross-site scripting attack, and you are developing in J2EE.

OK, do you call a friend? Do you fire up a wiki? Do you go to Google? Do you pull out a manual or an internal checklist, or some type of gargantuan knowledgebase? And how long will that take you?
TeamMentor alleviates the need to do any of this or open up a bunch of distributed apps – you just search in TeamMentor, find the content you need, fix the problem and continue coding.

With so many vulnerabilities in existence, numerous languages and technologies to write code in and the demands between producing bug and vulnerability-free software and meeting deadlines, you need a solution that tells you how to fix these issues quickly…oh, and something that will let you map what you are doing to meet your specific software security requirements within your organization.

Our first session in the series kicks off this week on November 17 with Dinis Cruz presenting how are you can drop your own superior for your own internal security policies into the application.

Why is this important? Well, the result of the re-architected customization capabilities now give you the ability to map your own internal security policies to the default software development guidance/3000+ content articles that ships with TeamMentor. So it will allow you search for guidance based on the category of vulnerability or development language, but remediate according to your organization’s specific policies. In essence, you can make TeamMentor yours.

Register for this week’s demo session with Dinis Cruz, Principal Security Engineer, who has led the build-out of TeamMentor.

Empower your developers! Map your software development practices directly to your security policies! Give them the opportunity to collaborate and streamline the code remediation process in real-time!

For additional information, pull down our new TeamMentor data sheet here, visit Dinis Cruz’s blog, or our web site for more detailed information.

Topics: application security

Tom Bain

Written by Tom Bain