Robohelp 9 security holes when creating webhelp

[Guest]

How can I assure a customer that the *webhelp* that I am producing with RoboHelp 9 does not have security holes related to:

• Cross site scripting: persistent, non-persistent, and DOM-based.
• Cross site framing: does the webhelp prevent itself from running within a frame.
• Is SQL injection a possible problem?
• Buffer overflow.
• Session management.  Require that authenticated users have a secure association with their session.
• Access control.
• Input validation.
• Output encoding/escaping.

Generally, what processes are in place to ensure that RoboHelp webhelp is free from security vulnerabilities?  Is this certified somehow?

Thanks!

[Jeff_Coatsworth]

Only assurance is that your version of RH9 is fully patched. Your assessor will test for vulnerabilities, but there are probably some freebie tools out there.