Dual Endpoint Workflow

The Record Reflected in the Dual-Endpoint Workflow

The record concerns whether Mphasis and QBE created, directed, tolerated, and relied upon a dual-endpoint workflow while denying compliant alternatives, and whether the QBE-issued laptop — an active endpoint to U.S. data — was left operationally unresolved.

The issue is not simply whether policies existed. The issue is whether enterprise-created infrastructure constraints, operational expectations, and ongoing management visibility resulted in a normalized dual-endpoint operating model involving a personal Mac workstation and a QBE-issued laptop.

The workflow reflected in the record includes QBE-related project work, PowerPoint deliverables, web-only access restrictions, personal-device workflow reliance, QBE-issued endpoint access, DLP escalation, protected complaints, and later litigation positions concerning the same operational sequence.

Viewed together with the related ECF filings, the record presents an operational question: can the conduct be fairly evaluated without considering the enterprise environment that produced it?

Operational Sequence

1. Workflow Direction. The record reflects assignment to QBE-related projects beginning in October 2024, including requested support for QBE deliverables and QBE PowerPoint work referenced in ECF 14-4.

2. Infrastructure Denial. The record reflects that no Mphasis laptop was provided, web-only restrictions were imposed, and repeated requests for compliant tooling or endpoint alignment were denied, deferred, or left unresolved.

3. Operational Reliance. Despite those constraints, deliverables continued, work product was accepted, management visibility continued, and the dual-endpoint workflow became operationally normalized.

4. DLP Escalation. The record references a potential DLP incident, DR110325111903, and contemporaneous escalation of workflow, infrastructure, and security concerns.

5. Protected Complaints. The record reflects repeated complaints involving cybersecurity concerns, policy inconsistencies, governance failures, compliance risks, and endpoint-management issues.

6. Later Recharacterization. After escalation and termination, the same workflow was later characterized as misconduct, unauthorized access, and policy violations.

7. The Forgotten QBE Laptop. The QBE-issued laptop remained operationally unresolved after termination and later became central to the endpoint-governance and litigation narrative.

Mphasis, QBE, and the Central Dispute

The central dispute is whether Mphasis and QBE created the dual-endpoint conditions, relied upon the resulting performance, denied compliant alternatives, and left the QBE laptop operationally unresolved — only to later recharacterize the same operational sequence as misconduct after protected complaints were raised.

The injunction narrative should therefore be evaluated against the full operational record, including the infrastructure constraints, management visibility, endpoint-governance issues, DLP escalation, protected complaints, and QBE laptop return history reflected in the related filings.

Topics Associated with the Dual-Endpoint Workflow

• Mphasis Corporation v. Albert Rojas
• Case 1:25-cv-03175-JMF-OTW
• QBE Laptop
• Forgotten QBE Laptop
• Dual-Endpoint Workflow
• Dual-Endpoint Environment
• No Mphasis Laptop
• Personal Mac Workflow
• QBE-Issued Laptop
• Endpoint Governance
• Endpoint Lifecycle Management
• Web-Only Restrictions
• SharePoint Access Limitations
• QBE PowerPoint Work
• QBE.pptx
• DLP Incident DR110325111903
• Security Escalation
• Protected Complaints
• Whistleblower Activity
• Operational Reliance
• Operational Recharacterization
• Retaliation and Pretext

Related Public-Record Pages

• ECF 14-4 – QBE.pptx Routing Record
• ECF 14-5 – DLP Escalation
• ECF 14-15 – QBE.pptx & Weekend Work Record
• ECF 14-36 – Dual-Endpoint Workflow
• ECF 14-38 – No Mphasis Laptop Issued
• ECF 221 – Forgotten QBE Laptop
• ECF 560 – Motion Concerning QBE.global
• ECF 560-1 – June 8, 2026 Email Attachment
• QBE / Mphasis Weekend Proposal
• Setting the Record Straight – QBE Legal NDA Record
• QBE in the Record

Public-Interest Context

This page is included as part of the QBE.global public-record archive. It is intended to organize publicly discussed operational events, governance questions, cybersecurity issues, endpoint-management concerns, and litigation-related materials reflected in the record.

Readers are encouraged to review the PDF, related filings, and underlying record directly and draw their own conclusions regarding Mphasis, QBE, dual-endpoint workflow conditions, endpoint governance, DLP escalation, protected complaints, and the operational sequence reflected in the litigation record.