Stream: Virtual Room 8
Time: 16:30 - 17:30
In the first section, Scott will cover how incorrect PC routine setup, incorrect SVC or PC parameter checking, incorrect index bounds checking, and incorrect length checking for buffer sizes can all lead to high severity security vulnerabilities and how to prevent it. In the second section, Mike will discuss how less obvious problems in authorized programs can compromise system integrity as well. We will also leave time for questions after each section.
There is currently no attachment for Don't be the one: How one line of code can compromise your system integrity
Scott has worked in z/OS development for many years specializing in security, cryptography, and system automation. Since joining the z/OS Secure Engineering Team, he has been innovating local testing of authorized services.
Mike is the z/OS Secure Engineering Team Leader. He started at IBM twenty three years ago working on TSO/E before being named TSO/E Team Leader in 2007. In 2013 he joined the Secure Engineering Team and in 2020 he was named to his current role. He enjoys breaking authorized programs and looking for evidence in IPCS. In his spare time he enjoys sports or movies.
Scott has worked in z/OS development for many years specializing in security, cryptography, and system automation. Since joining the z/OS Secure Engineering Team, he has been innovating local testing of authorized services.
Mike is the z/OS Secure Engineering Team Leader. He started at IBM twenty three years ago working on TSO/E before being named TSO/E Team Leader in 2007. In 2013 he joined the Secure Engineering Team and in 2020 he was named to his current role. He enjoys breaking authorized programs and looking for evidence in IPCS. In his spare time he enjoys sports or movies.
Click here to give some Feedback so we can make it even better next year!