BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PYVOBJECT//NONSGML Version 1//EN
BEGIN:VTIMEZONE
TZID:Asia/Calcutta
BEGIN:STANDARD
DTSTART:20000101T000000
RRULE:FREQ=YEARLY;BYMONTH=1
TZNAME:IST
TZOFFSETFROM:+0500
TZOFFSETTO:+0500
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:20260916T063725Z - 46430@me281a.odoo.com
DTSTART;TZID=Asia/Calcutta:20260918T203000
DTEND;TZID=Asia/Calcutta:20260918T213000
CREATED:20260916T063725Z
DESCRIPTION:<a href="https://www.gisacouncil.com/event/who-changed-the-prod
 uction-database-72">Who Changed the Production Database?</a>\nProduction d
 atabase changes can have serious consequences — from incorrect business 
 data and system failures to security incidents and compliance issues. But 
 when a change happens directly in production\, can you actually determine 
 who made it\, what was changed\, why it was changed\, and whether it was a
 uthorized? This practical session explores how IT Auditors\, Security prof
 essionals\, and GRC teams can audit direct database access\, production ch
 anges\, and data integrity. Participants will learn how to identify unauth
 orized access\, review database activity and change logs\, assess controls
  around privileged access\, and determine whether production changes are p
 roperly authorized\, documented\, and traceable. What You Will Learn How d
 irect production database access creates audit and security risks Identify
 ing and reviewing privileged database access Auditing database activity lo
 gs and user activity Detecting unauthorized production changes Assessing c
 hange authorization and approval controls Checking data integrity and iden
 tifying suspicious modifications Reviewing segregation of duties around da
 tabase administration Evaluating monitoring\, logging\, and alerting contr
 ols Practical approaches to documenting audit findings Real-world scenario
 s involving unauthorized database changes Who Should Attend? This session 
 is ideal for IT Auditors\, Information Security professionals\, GRC profes
 sionals\, Database Administrators\, Risk and Compliance teams\, and anyone
  responsible for production systems and access controls. Takeaway: Learn h
 ow to follow the evidence and answer the question every auditor wants to r
 esolve: Who changed the production database?
DTSTAMP:20260916T063725Z
LOCATION:GISA COUNCIL FOR SECURITY RESEARCH AND EDUCATION\, SMC SERVICES\, 
 B/502 PANCHVATI PARADISE OPP. R.A.F. CAMP\, VASTRAL\, Ahmedabad 382418\, G
 ujarat GJ\, India
SUMMARY:Who Changed the Production Database?
X-ALT-DESC;FMTTYPE=text/html:<a href="https://www.gisacouncil.com/event/who
 -changed-the-production-database-72">Who Changed the Production Database?<
 /a>\nProduction database changes can have serious consequences — from in
 correct business data and system failures to security incidents and compli
 ance issues. But when a change happens directly in production\, can you ac
 tually determine who made it\, what was changed\, why it was changed\, and
  whether it was authorized? This practical session explores how IT Auditor
 s\, Security professionals\, and GRC teams can audit direct database acces
 s\, production changes\, and data integrity. Participants will learn how t
 o identify unauthorized access\, review database activity and change logs\
 , assess controls around privileged access\, and determine whether product
 ion changes are properly authorized\, documented\, and traceable. What You
  Will Learn How direct production database access creates audit and securi
 ty risks Identifying and reviewing privileged database access Auditing dat
 abase activity logs and user activity Detecting unauthorized production ch
 anges Assessing change authorization and approval controls Checking data i
 ntegrity and identifying suspicious modifications Reviewing segregation of
  duties around database administration Evaluating monitoring\, logging\, a
 nd alerting controls Practical approaches to documenting audit findings Re
 al-world scenarios involving unauthorized database changes Who Should Atte
 nd? This session is ideal for IT Auditors\, Information Security professio
 nals\, GRC professionals\, Database Administrators\, Risk and Compliance t
 eams\, and anyone responsible for production systems and access controls. 
 Takeaway: Learn how to follow the evidence and answer the question every a
 uditor wants to resolve: Who changed the production database?
END:VEVENT
END:VCALENDAR