Starfleet Security (USS Enterprise-D)

Through the collective action of security personnel summoned to detain Clemens.

Operating under the authority of senior officers (Riker) to enforce containment protocols, with no independent agency in this event.

Reinforces Starfleet’s commitment to temporal integrity and the crew’s ability to respond swiftly to threats, even in unconventional circumstances.

Through Worf and the security N.D.s, executing tactical commands and securing the bridge.

Operating under the crew's command, enforcing countermeasures to contain the alien threat.

The security team's actions demonstrate the crew's ability to exploit the ship's systems against the aliens, reinforcing institutional power and unity.

The team operates with disciplined efficiency, reflecting their training and loyalty to the crew.

Through Worf’s engagement of the turbolift override controls and the non-descript security officers rushing to secure the bridge.

Supportive and reactive, acting under the bridge crew’s leadership to contain the threat.

The security team’s actions reinforce Starfleet’s ability to respond to internal threats, demonstrating the crew’s discipline and unity in crises. Their role highlights the importance of institutional protocols in countering possession scenarios.

None explicitly shown, but implied cohesion under Worf’s leadership and Riker’s authority.

Through Worf and two unnamed security officers, who engage in a phaser firefight with the possessed crew but are quickly stunned and incapacitated.

Operating under constraint, as the possessed crew’s technical and tactical advantages give them the upper hand. The security team is reactive, responding to the threat rather than anticipating it.

The security team’s failure highlights the Enterprise’s vulnerability to insider threats and the need for more robust protocols to handle possession scenarios.

The team operates under a clear chain of command, with Worf leading the charge and the unnamed officers following his orders. Their unity is strong, but their lack of preparation for this specific threat leaves them at a disadvantage.

Through Worf and two security officers acting as a rapid-response team, executing orders from senior staff (Picard, Riker) and engaging the possessed crew in Ten Forward.

Operating under constraint—the possessed crew's immunity to phaser stuns renders Starfleet Security's standard tactics ineffective. They are outmatched, forced to rely on brute force and desperation rather than institutional protocol.

The security team's failure to stop the possessed crew exposes the limits of Starfleet's preparedness for internal threats. Their actions (or lack thereof) force the organization to reconsider its protocols, particularly in scenarios where crew members are compromised by non-corporeal entities.

Tension between institutional protocol (phaser stuns) and the reality of the threat (possessed crew's invulnerability). Worf's Klingon instincts drive him to fight despite the odds, while the security officers follow orders to the end, even in a losing battle.

Through Riker’s order to ‘stand by,’ which activates the security teams as a latent force. Their readiness is a tangible presence on the bridge, even if they are not physically present in this moment.

Operating under the authority of Riker and the bridge crew, the security teams are a controlled force, their actions dictated by command decisions. Their power lies in their ability to respond swiftly and decisively to threats, but they are also constrained by the need to avoid harming the possessed officers, whose bodies are being used against their will.

The security team’s role in this crisis highlights the tension between Starfleet’s ideals of non-violence and the harsh realities of self-defense. Their actions will test the crew’s ability to balance duty with compassion, a challenge that lies at the heart of this episode’s moral dilemmas.

The security teams operate as a disciplined unit, but individual members may grapple with the ethical implications of their orders. Some may hesitate to fire on possessed crewmates, while others may be fully committed to following Riker’s commands without question. These internal tensions could affect their effectiveness in the coming confrontation.

Through the possessed crew members’ actions (off-screen) and the broader threat they pose to the *Enterprise*’s security.

Operating as an external force challenging the *Enterprise*’s institutional control, exploiting vulnerabilities in its protocols and crew.

The Ux-Mal’s involvement in this event highlights the fragility of the *Enterprise*’s defenses when faced with an adaptive, non-corporeal threat. Their ability to infiltrate and manipulate the ship’s systems from within undermines the institution’s reliance on protocols, hierarchy, and technology, forcing the crew to confront the limits of their control.

The Ux-Mal operate as a unified but potentially fractious collective, with internal tensions (e.g., suspicion, paranoia) that Picard later exploits. Their actions in this event reflect a calculated, ruthless strategy to escape, even as their possession of the crew creates instability among their hosts.