SAP development systems are an often underestimated entry point for attacks.
Welcome to the final installment of our series on the Dangers in SAP Transport Management. In our final post, we’ll focus on how an attacker could leverage logical file names and logical OS commands within SAP transports to access, modify and exfiltrate data.
This is part three of our blog series on the Dangers in SAP Transport Management. In part one, we give an intro to SAP Transports. In part two, we went over the starting point of this attack, the transaction SU24. In this third installment, we’re focused on the manipulation of job management and its associated risks to SAP Transports.
The first article of this series spoke about the global deactivation of authorization checks for single authorization objects per transport. A similar risk results from the possibility of deactivating authorization checks transaction-specifically. With this method, it is even more difficult to detect an attack, as the impact can be limited to one transaction.
Across industries, organizations implement software solutions, IT controls, policies and procedures to secure their mission-critical applications. While dev, test and QA systems are not ignored, they are not always treated as equal.