Skip to content

1.05-Partner Engagements

Partner Engagements Task

Conditions

  • Given a mission to deploy a IR Team in support of Guardnet, State IT systems, or other organization as directedby the Governor
  • Response effort if localized and a Type I / II Federal Disaster Response has not been declared

Standards

  • Verify personnel status: State Active Duty (SAD) or T32
  • Work with mission partner POC to understand support requirements
  • The mission partner is in charge
  • Coordinate with mission partner POC to sign MOUs as appropriate
  • Coordinate with mission partner POC to sign NDAs as appropriate
  • Provide updates to mission partner POC as requested or within their reporting timelines
  • Make recommendations when appropriate to the mission partner POC
  • Do not interact with or change mission partner systems unless receiving permission, preferably written
  • Be prepared to share any/all findings with the mission partner; reporting could be summary, technical, or both
  • Should on-mission personnel identify potentially illegal activities or other violations, inform the mission partnerimmediately and appropriate authorities

End State

The on-mission IR Team establishes and maintains a positive working relationship with the support mission partner.

Notes

It is the prerogative of mission partner to approve/disapprove system changes; you may disagree with mission partner but ultimately it is their system

Manual Steps

Running Script

Dependencies

Other available tools

References

FM 3-13: Information Operations (Chapter 9, Soldier and Leader Engagements)

Revision History