One Step From a Developer's Keyboard to Live | CISA Domain 4 Lesson 6

Описание: A developer needed a quick fix, so they logged straight into production with the admin access they have always had, edited the live code, and moved on. No separate test, no release record. The path from a developer's keyboard to live was a single step. Release and patch management is about controlling that path.

In this lesson: why development, test and production are kept separate, how patches are prioritised by risk, and why standing developer access to production is a release and segregation finding.

This is lesson 6 of Domain 4, IS operations and business resilience, which is 26% of the exam.

🎓 Free CISA course: https://marcoweb.org/training/
📝 Practice exams by domain: https://marcoweb.org/training/exam/
🛠️ Free ITGC self-assessment tool: https://itgc.marcoweb.org

CHAPTERS (measured from the generated audio, accurate)
0:00 A one-step path to live
0:34 Separate the environments
0:57 Only tested code, separated duties
1:20 Prioritise patches by risk
1:56 Patches are changes too
2:17 Standing prod access is the gap
2:53 The takeaway

Independent training produced by Marco Cavani. Not affiliated with, endorsed by, or sponsored by ISACA. CISA is a registered trademark of ISACA. Practice questions are written for this course and are not reproduced from ISACA materials.

#CISA #ITAudit #PatchManagement #InformationSystemsAudit #AuditTraining #CISAExam #ReleaseManagement #ITOperations #InternalAudit