Logistics Identity and Service-Recovery Control Architect

The mandate

The defined problem is a control architecture in which identity access and service recovery are designed separately, leaving uncertainty about who can restore critical logistics information services and under what permissions. The consultant will deliver an Identity and Recovery Control Architecture for an agreed service perimeter. It must show the dependency and evidence behind restore capability, not merely recommend a new security tool.

Identity and recovery architecture work begins on 19 October 2026 and spans six months, with four days weekly reserved for Bengaluru design sessions, remote technical analysis and planned India service workshops. The architecture package contains the identity-dependency map, privileged restore-access roles, control sequence and authorised rehearsal specification. Any production implementation must receive a separate scope decision through change control rather than being inferred from design approval.

Milestone one on 18 December 2026 contains an accepted service and identity baseline, identifying recovery access that is undocumented or over-privileged. Milestone two, due 18 February 2027, delivers the reviewed architecture and tested control sequence in an authorised environment. Milestone three on 18 April 2027 is the corrected design, witnessed recovery-access rehearsal and retained-owner reproduction of architecture decisions for a changed service dependency.

The transformation sponsor and security design authority jointly accept the artifacts, with service owners confirming operational relevance. Acceptance requires recovery permissions to be justified, emergency access to have approval and revocation evidence, and the selected restore sequence to meet signed completeness criteria. Exclusions must remain explicit. A successful login or backup restore alone does not prove that the architecture supports a secure service recovery.

The sponsor supplies inventories, access policies, recovery records, approved test capacity and named reviewers. The consultant does not operate incident response, procure a platform, promise customer availability or redesign maritime operations. New services and production implementation need separately authorised scope and fees. The engagement closes on accepted architecture and rehearsal transfer, leaving ongoing access and service decisions internally accountable.

What you will own

• Map selected logistics service and identity dependencies, identifying where recovery relies on credentials, approval routes or infrastructure conditions not reflected in the current service plan.
• Design privileged recovery-access roles with necessity, duration and revocation evidence, preserving segregation between emergency restoration capability and permanent administrative authority.
• Construct the restore-control sequence linking identity readiness, configuration and service validation, documenting dependencies and exclusions that prevent a limited test from implying complete resilience.
• Validate architecture choices with security and service owners, recording the decision basis and approval requirements before any design is described as ready for implementation.
• Run an authorised recovery-access rehearsal, testing approval, use and withdrawal of permissions alongside the agreed service restore evidence and completeness criteria.
• Transfer the architecture and decision method through retained-owner replay for a changed dependency, correcting design ambiguities and identifying implementation work outside the project fee.

Candidate qualifications

• Demonstrate twenty-two or more years in technology with substantive infrastructure, identity or security-architecture delivery and senior functional responsibility. Present a control architecture you personally developed, the recovery dependency it exposed and how design authorities accepted it. The role requires technical authorship as well as leadership-level interpretation.
• Show practical expertise in identity, privileged access, virtualised or cloud infrastructure and service recovery. Explain a case where restore capability failed because the assumed permissions or configuration dependencies were unavailable, and describe the approved design and evidence that corrected the weakness.
• Bring architecture governance and assurance discipline, including clear boundaries between design, implementation and tested capability. Provide an acceptance criterion you strengthened because a superficially successful rehearsal did not establish secure recovery. Candidates must preserve emergency access controls rather than treat disruption as a reason for unrestricted administration.
• Prove fixed-fee design delivery with controlled test approval, secure source records and retained-owner transfer. Describe handling of production implementation requests or new services without silently broadening authority or milestones. Logistics context is valuable, but the consultant does not assume maritime operating powers, customer commitment authority or ownership of live incident response.

Application

Applications for this mandate are received in one way only: through the India Board Terminal's application process. It is automated end to end. Your Executive Passport travels to the mandate holder in its confidential form, your answers to the three questions below are read before anything else in your file, and every stage that follows is recorded on your applications page.

There is no address to write to and no intermediary to call. The mandate holder reads what the Terminal delivers and nothing else, which is what keeps the process the same for every applicant and keeps your name out of it until you release it. Applications close on 9 October 2026. Mandate reference PCT-CON-2026-IND-57.