Sourced aerospace and automotive production context
Aircraft, vehicles, and controlled manufacturing: Workday Security
Charleston's consolidated plan identifies aerospace and automotive production as advanced sectors in the regional economy and links both to large manufacturing and supplier networks. Translate the operating setting into security groups, domain permissions, business-process policies, organization constraints, and sensitive fields. Ask how users complete work under least privilege. Aircraft and vehicle operations can connect approved designs, parts, suppliers, equipment, production orders, inspections, serial history, maintenance, safety evidence, and release authority.
Evidence to request: Use an access-design exercise with worker groups, domains, business processes, sensitive fields, and organization constraints. Trace the aircraft, vehicle, or component from approved configuration and sourced material through production, inspection, serial record, discrepancy, delivery, maintenance, and authorized release.
Sourced biotechnology and life sciences context
Research, clinical, and regulated product records: Workday Security
The Charleston plan describes a life-sciences cluster built around research laboratories, medical-device work, pharmaceutical manufacturing, and the Medical University of South Carolina. Define joiner, mover, leaver, service-account, and integration access across Workday and identity systems. Require evidence from provisioning, authentication, access reviews, and exception handling. Life-sciences systems may join samples, instruments, clinical data, device configurations, product batches, validation, quality events, complaints, and regulated retention.
Evidence to request: Review a provisioning or integration-security defect with identity, scope, logs, correction, retest, and user impact. Name the research, clinical, or product outcome, sample or patient identity, instrument interface, validation test, quality gate, traceability rule, complaint path, and approval owner.
Sourced information technology and cybersecurity context
Software, data, and defence-service boundaries: Workday Security
Charleston's plan also identifies information technology activity across cybersecurity, software services, and data analytics, including firms that support defence work. Set audit and release ownership. Candidates should explain how they analyze access, resolve conflicts, migrate changes, test populations, retain evidence, and verify permissions after an organization or process change. Technology and cyber teams can cross product code, client systems, sensitive data, identity, threat monitoring, incident response, service levels, and retained evidence.
Evidence to request: Ask for an audit finding or tenant release the consultant handled, including analysis, configuration, population testing, evidence, and follow-up review. Set the product, client, or mission boundary, data classification, trust model, production authority, monitoring evidence, incident path, delivery artifact, and support obligation.