Sourced open data and public reuse context
Source records, publishing, and corrections: Oracle Security
Open Data BR provides City-Parish data for public analysis, web visualizations, applications, department coordination, and resident access. Translate the operating setting into roles, privileges, data access, duty separation, service accounts, and sensitive transactions. Ask how users complete assigned work under the proposed controls. A public-data service needs named owners for source records, publication rules, refresh timing, metadata, legal review, corrections, and downstream applications that the publishing team does not control.
Evidence to request: Use an access-design exercise with job duties, application roles, data scope, conflicts, service accounts, and approval owners. Identify each source system, dataset owner, publication test, refresh schedule, restricted field, correction route, consumer, and support handoff connected to the role.
Sourced enterprise applications and infrastructure context
Shared services across departments: Oracle Security
Baton Rouge Information Services lists application development, server administration, network management, and consolidation of department technology among its responsibilities. Define joiner, mover, leaver, request, approval, provisioning, review, and removal flows across Oracle applications and identity services. Require evidence from connectors, workflows, logs, and exception handling. A shared service may support departments with separate case records, approvals, retention rules, operating hours, budgets, and legacy systems while one central team owns infrastructure and support.
Evidence to request: Review an identity or provisioning defect with source identity, target account, logs, correction, retest, and user impact. Name the departments, user groups, service owner, application and hosting boundary, approval path, maintenance window, legacy connections, and acceptance evidence.
Sourced cybersecurity and geographic data context
Identity, location, and disclosure boundaries: Oracle Security
The Information Services department identifies cybersecurity and geographic information systems as City-Parish functions and describes work on maps, data, and applications. Set audit and release ownership. Candidates should explain conflict analysis, role redesign, migration, population testing, evidence retention, emergency access, and follow-up review. Constituent and location records can cross identity, field access, map layers, integrations, operational use, audit logs, and public-disclosure rules that require separate review owners.
Evidence to request: Ask for an audit finding or application release the consultant handled, including analysis, configuration, population testing, evidence, and closure. Define the identity authority, protected records, geographic layers, access groups, public boundary, retained logs, incident route, and review required after a system change.