Hosts Chandra and Paul continue their deep dive into JD Edwards (JDE) security with guests Andrew Ostdiek, Matthias Freitag, and Nimesh Patel. The conversation kicks off with the importance of naming conventions when managing User Defined Objects (UDOs) and how early oversight in this area can prevent disorganization and headaches down the line. The panel shares candid stories and lessons learned, emphasizing the need for governance, simplicity, and structure to avoid chaos and maintain effective security management as JDE capabilities expand. As the episode unfolds, the group discusses the increasing pressure of audits, evolving security roles, and best practices for tackling the constant changes that JDE environments demand. They stress keeping security models as straightforward as possible to make troubleshooting and implementing new requirements manageable—highlighting that complexity can become an obstacle.  

06:35 Why Naming Conventions Matter   

10:22 Governance: It’s Not just for Data  

14:50 Continuous Security Evolution 

16:33 The Cost of Complexity 

19:05 Audit Pressure is Real 

28:20 Have you achieved your Security Dream State? 

36:35 Midwesternism of the Day 

Resources: 

Security Administration Guide: https://docs.oracle.com/en/applications/jd-edwards/administration/9.2.x/eotsc/toc.htm 

If you have concerns or feedback on this episode or ideas for future episodes, please contact us at thejdeconnection@questoraclecommunity.org.