Avoiding Compliance Issues in ABAP code - Virtual Forge

More documents

Recommendations

Info

ABAP Vulnerabilities (2)Client SeparationPPT Masterfolie* OPEN SQLzur Erstellung von PräsentationenDELETE FROM usr02 CLIENT SPECIFIED.* Native SQLEXEC SQL.DELETE FROM usr02.ENDEXEC.* ABAP Database Connectivity (ADBC)CALL FUNCTION 'DB_EXECUTE_SQL'EXPORTINGstmt = 'DELETE FROM usr02'.© 2012 Virtual Forge GmbH | www.virtualforge.com | All rights reserved.
ABAP Risks (3)Development ProcessPPT Masterfoliezur Erstellung von PräsentationenControlled Development & Quality AssuranceSystem SeparationTransportTransportDEV TEST PROD© 2010 Virtual Forge GmbH. All rights reserved.Risks• Bypassing Quality Assurance• Developing Code on the Productive System© 2012 Virtual Forge GmbH | www.virtualforge.com | All rights reserved.
Page 1 and 2: Andreas WiegensteinDr. Markus Schum
Page 3: My car, my house, my boat, …Andre
Page 7 and 8: The Attack Surface of ABAPPPT Maste
Page 10 and 11: ABAP Vulnerabilities (1a)Authorizat
Page 12 and 13: ABAP Vulnerabilities (1c)Authorizat
Page 16 and 17: ABAP Vulnerabilities (3)Development
Page 18 and 19: ABAP Vulnerabilities (4)Operating S
Page 20 and 21: 2. PPT Compliance Masterfolie Risks
Page 22 and 23: ABAP Code RisksExemplary technical
Page 24 and 25: Risks of SQL Injection (APP-06)Exem
Page 26 and 27: 3. PPT ABAP Masterfolie Security at
Page 28 and 29: The SDP Maturity ModelPPT Masterfol
Page 30 and 31: 4. PPT Practical Masterfolie ABAP S
Page 32 and 33: Externe ABAP DevelopmentPPT Masterf
Page 34 and 35: ABAP Security ResourcesPPT Masterfo

Avoiding Compliance Issues in ABAP code - Virtual Forge

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?