Does Powerbuilder 2017 support Fortify code scans?
Does Powerbuilder 2017 support Fortify code scans?
Would it really be a valid test to scan code generated into a different language?
What if it finds a problem that is not due to the way you coded it in PowerScript but how the language convertor coded it.
Hi Randy,
The question is not does PB support Fortify but rather the other way around. To best of my knowledge, Fortify doesn't support scanning PowerScript.
But if you convert your PowerScript to another language that Fortify does support you could effectively get your PowerScript code scanned by Fortify that way.
Chris has a hack for generating C++ from PowerScript or you could use the new PowerScript Migrator in PB 2019 R2 to convert your PowerScript to C#. https://youtu.be/Bcn6tt7H-Kk?t=69
Regards,
Armeen
sorry I am just coming back to this now
what do you mean
"ts - you can trap the generated C++ and/or C# code and then feed that into Fortify. "
thanks for any assistance
Hi Randy;
Unfortunately, the HP Fortify product does not support the PowerScript language.
As a workaround though, PB does emit C++ or C# depending on whether you are a) compiling to machine code; b) deploying as a Winform app; c) deploying a .NET Assembly; or d) deploying Web Service. During these compilation / deployments - you can trap the generated C++ and/or C# code and then feed that into Fortify. The generated code is basically a 100% reflection of the PowerScript commands. Thus, the Fortify scan of the generated C++ / C# source should expose any vulnerability issues from the static perspective.
Note: the Winform deployment option was removed in PB 2017 but was present on PB versions 11.x through 12.6.
Regards ... Chris