Faith-Based Daily Awareness Post 5 May 2026

These updates are shared to help raise the situational awareness of Faith-Based organizations to best defend against and mitigate the impacts from all-hazards threats including physical security, cybersecurity, and natural disasters.

NY: New York Church of Scientology speedrunning incident

A group of about 25 individuals forced their way into a Church of Scientology building in Manhattan, causing property damage and injuring a staff member in an incident linked to a viral “speedrunning” social media trend adapted from gaming culture. Similarly, a 16-year-old was arrested for breach of the peace after attempting a similar “speedrun” at Vancouver’s Church of Scientology but was later released without charges. Authorities say similar incidents have occurred in other cities, raising concerns about trespassing, mischief, and potential break-and-enter charges, as participants attempt to gain entry to buildings for online attention.

Analyst Comments: This appears to be a niche but persistent trend primarily targeting the Church of Scientology, likely driven by the organization’s high public profile, controlled access to facilities, and existing online attention. At this stage, there is little to suggest the behavior is broadly transferring across faith communities.

However, the underlying dynamic of social media-driven stunts escalating into coordinated trespass, disruption, and potential violence has wider relevance. Even if copycat activity remains unlikely, security teams at other religious institutions should take note of how quickly online trends can mobilize groups, overwhelm access points, and create safety risks for staff and visitors. Basic access control measures, staff awareness, and incident response planning remain the most practical takeaways, particularly for institutions with open public access or perceived exclusivity.

10 AI Tools Your Church Staff Needs to Know About Right Now In 2026

This article outlines 10 AI tools that pastors and church staff can use in 2026 to streamline ministry operations, communications, and content creation.

It highlights tools like:

• ai — Meeting transcription and action-item tracking for staff and leadership meetings
• Google NotebookLM — Turns documents into audio overviews, study materials, and training content
• Agenda Hero — Converts event lists into shareable, one-click calendar entries
• ai — Generates church graphics, social media visuals, and bulletin designs with readable text
• ManyChat — Automates guest follow-ups, messaging, and registrations across SMS and social platforms
• ai — Converts written ideas into simple diagrams and visual frameworks
• Gamma — Quickly builds presentations, one-pagers, and event materials from prompts or outlines
• Claude for Chrome — Assists with web browsing, research summaries, and email drafting in real time
• Descript / Eddie.ai — Simplifies video editing and automatically creates sermon clips and highlights
• dev — Builds simple web apps (like sign-ups or dashboards) from plain-language descriptions

The main takeaway is that churches should avoid adopting multiple tools at once and instead start with one practical use case such as improving guest follow-up, meeting documentation, or content creation to build familiarity and gradually integrate AI into everyday ministry workflows.

Analyst Comments: From a risk and governance perspective, the proliferation of AI tools into pastoral and church administrative workflows raises familiar but often under-addressed concerns around data security, privacy, and institutional control of information. Many of these platforms process sensitive content such as counseling-related notes, donor communications, membership data, and internal leadership discussions, often through third-party cloud systems with varying retention and training policies. Without clear guidance, organizations risk informal or ad hoc adoption, where individual staff introduce tools faster than governance frameworks can assess data handling, vendor risk, or compliance implications.

For houses of worship (HOWs), the key issue is not whether to adopt AI, but how deliberately it is introduced. Decisions should be anchored in defined use cases, data classification rules, and approved toolsets rather than personal preference or convenience. Leadership teams should also consider minimum standards for vendor review, particularly around data usage for model training, storage location, and access controls. In practice, this means treating AI tools less like productivity apps and more like third-party data processors that require oversight, boundaries, and periodic reassessment as both the technology and threat landscape evolve.

FB-ISAO Education Series | Building an Intelligence Team for your House of Worship

NEXT SESSION >> May 6, 2026, 12:00 PM ET: Expanding your horizon to consider additional atypical threats, man-made and natural disasters, to prepare for all-hazards.

Register here.