First Nations Community Security: A Practical Guide for Councils & Administrators

Understanding the Jurisdictional Landscape

Security on reserve lands sits at the intersection of several legal orders. The Indian Act grants band councils authority to pass by-laws related to public order and safety, while the Criminal Code of Canada remains the overarching federal criminal law. Depending on the province, a community may also fall within the operational area of an RCMP detachment, a provincial police service such as the Ontario Provincial Police or Sûreté du Québec, or a dedicated First Nations police service operating under the First Nations Policing Program administered by Public Safety Canada. Understanding which authority has jurisdiction over which type of incident is the necessary first step before any security programme is designed.

Confusion about jurisdiction is one of the most common sources of friction when a security incident occurs. A written memorandum of understanding between the band council, the relevant police service, and any contracted security provider clarifies response protocols before an incident occurs, rather than during one. Councils that have invested in this groundwork consistently report smoother coordination during after-hours disturbances, access disputes, and emergencies involving band facilities.

• Identify which police service holds the primary law enforcement mandate on your territory and confirm this in writing.
• Review existing band by-laws related to public order and determine whether they require updating before a security programme launches.
• Establish a written protocol that defines when security personnel call police, when they manage a situation independently, and when they escalate to band administration.
• Confirm whether your community falls under a tripartite policing agreement and understand what obligations that creates for your security provider.
• Retain legal counsel familiar with Indigenous governance when drafting inter-agency agreements — template documents from non-Indigenous contexts often contain assumptions that do not translate.

Embedding Cultural Protocols into Security Operations

A security programme that ignores the cultural fabric of a First Nations community will struggle to earn the trust of the membership it is meant to protect. This is not a soft consideration — it has direct operational consequences. Security personnel who do not understand the significance of ceremonial gatherings, seasonal activities, elder protocols, or the role of traditional governance structures may inadvertently create confrontations that a culturally informed officer would have de-escalated through acknowledgement and respect alone. Councils should insist that any security provider demonstrate a concrete, documented approach to cultural orientation, not simply assert that their staff are culturally sensitive.

Cultural protocol training should be developed in partnership with knowledge keepers and community leadership, not sourced from a generic diversity module. The content will differ meaningfully between, for example, a Haudenosaunee community in southern Ontario and a Dene community in the Northwest Territories. Access restrictions during ceremonies, protocols around elder spaces, and expectations for how disagreements are addressed publicly are all community-specific and must be reflected in the security provider's site-specific operational plan.

• Require that cultural orientation for security personnel be delivered or approved by a community-designated cultural liaison, not solely by the security company.
• Document cultural protocols in the site-specific post orders so knowledge is not lost when individual officers rotate.
• Build a review cycle into contracts so that protocols can be updated when community practices or leadership directives change.
• Establish a clear escalation path for situations where a security officer is uncertain whether an action conflicts with cultural practice.

Licensing, Training Standards, and Contractor Accountability

Security companies operating in most Canadian provinces must hold a valid security business licence and employ officers who hold individual security guard licences under the applicable provincial statute. In Ontario, this is governed by the Private Security and Investigative Services Act, 2005. In British Columbia, the Security Services Act sets out equivalent requirements. Alberta operates under the Security Services and Investigators Act. Councils and administrators should verify that any contracted security provider holds the appropriate provincial licence and that each officer deployed on community property holds a valid individual licence. Photocopies of these documents should be retained on file and reviewed at contract renewal.

Beyond baseline licensing, councils should evaluate what additional training standards a provider can demonstrate. First aid and CPR certification, crisis intervention and de-escalation training, and familiarity with the Mental Health Act provisions relevant to their province are all meaningful indicators of officer preparedness. For communities that have experienced challenges related to substance use or mental health crises — which many communities have, for well-documented historical reasons — these competencies are not optional enhancements; they are core requirements.

• Request copies of both the security business licence and a sample individual guard licence at the proposal stage, before any contract is signed.
• Confirm that training records are maintained and available for audit, as insurers and federal funders may request them.
• Ask specifically about de-escalation and mental health crisis training — not whether the company offers it, but whether the officers assigned to your site have completed it.
• Include a contractual requirement that the provider notify the council within a defined timeframe if any officer's licence lapses or is suspended.
• Consider requiring that supervisors or site managers hold a security supervisor designation where the provincial framework recognises one.

Coordinating with Tribal Police and the RCMP

Where a First Nations community has its own police service, the relationship between that service and contracted security personnel requires careful definition. Tribal police officers are sworn peace officers with arrest authority. Security personnel are not. The distinction matters enormously when a situation escalates, and it must be understood by everyone involved before an incident occurs. A joint protocol meeting between band administration, the tribal police chief or detachment commander, and the security provider's operations manager is a practical starting point. The output of that meeting should be a written document, reviewed annually, that describes response thresholds, communication channels, and reporting obligations.

In communities policed by the RCMP under a provincial or municipal policing agreement, the dynamics differ. RCMP detachments may cover large geographic areas and response times can be significant. In these contexts, security personnel often serve as a first-response presence, documenting incidents and maintaining stability until sworn officers arrive. This role should be defined explicitly, and security personnel should not be positioned — formally or informally — as a substitute for adequate policing resources. Councils that conflate the two functions risk creating liability exposure and, more importantly, unsafe conditions for their community members and for the security officers themselves.

Meeting Audit and Insurance Requirements

Band councils that receive federal or provincial funding for infrastructure, housing, health, or community services are subject to audit requirements that increasingly include questions about security governance. Funding agreements may specify that adequate security measures be in place for funded facilities, and auditors will look for documented evidence of those measures. This means contracts, not verbal arrangements. It means incident reports, not informal notes. It means a written security plan that describes the scope of coverage, the staffing model, the reporting structure, and the escalation protocols. Councils that cannot produce this documentation on request face compliance risk that extends beyond the security function itself.

Insurance underwriters for community assets — including band-owned buildings, vehicles, and community centres — are similarly attentive to whether a formal security programme exists and whether it is properly documented. Gaps in coverage, inadequate incident documentation, or the absence of a licensed provider can affect premium calculations and, in some cases, coverage eligibility. Administrators are well advised to share their security programme documentation with their insurance broker proactively, rather than waiting for a claim situation to surface these questions.

• Maintain a current written security plan and update it whenever staffing models, facility use, or community circumstances change materially.
• Ensure all incident reports are completed by officers at the time of the incident, retained systematically, and accessible to band administration.
• Provide your insurance broker with a copy of your security contract and post orders annually so coverage assumptions can be validated.
• Cross-reference security documentation requirements against the specific language of your federal or provincial funding agreements — requirements vary by programme.
• Schedule an annual review with your security provider that includes a documentation audit, not just an operational debrief.
• Confirm that your provider carries adequate commercial general liability insurance and that the band council is named as an additional insured on that policy.