Perl got involved in this as it recieves the external POST verifies that it's XML, logs things, and sends a response to the client. It then does the actual POST to the SAP BC system, instead of a direct customer POST to BC.
After several posts to the Monsatry, and some very useful tips back we now have a functioning system. Many thanks in arrears...
Ovid's recent (OT) Security Rant has made me fearful. I didn't design the system, but as we found out in testing already, the SAP BC system is quite fragile, and I don't want someone placing an XML file (deliberatly or accidentally) into the system that will break the underlying DB.
Last time I looked there wasn't a stable Perl XML validator, plus if the XML isn't valid BC will reject it, my really worry is with a valid XML file that gets imported sucessfully into the DB and breaks the underlying SAP system.
If I run the XML file though a "de-tainting like" process, only letting through letters, numbers, and enough symbols to maintain valid XML, is this safe enough or is it still possible to comprimise the the DB?
Many thanks in advance for any comments. I know you can't be 100% secure, but I'd like to think we are as secure as is sensible.
It's probably just me being paranoid, but no one else at work seems to be as worried about security as I am.....
In reply to How to protect backend DB from hacks or accidents by ajt
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |