Below are two informative info-graphics from the Cybersecurity and Infrastructure Security Agency (CISA). They depict the IoT risk landscape and IoT device data flow.
☑️ Eclectic smatterings of information, resources and opinions ☑️
Below are two informative info-graphics from the Cybersecurity and Infrastructure Security Agency (CISA). They depict the IoT risk landscape and IoT device data flow.
Even organizations that have not yet experienced a known incident face serious challenges managing their IoT systems. Devices are frequently deployed across departments and facilities, added rapidly to support new initiatives, and not always inventoried or governed by consistent security standards. The result is classic “device sprawl”: too many devices, in too many places, with too little centralized visibility. For the public sector, where systems often support critical services, this sprawl can translate directly into operational and safety risks.
To respond, users need to treat mobile and IoT security as a core element of their cybersecurity posture. That means maintaining asset inventories, enforcing configuration baselines, segmenting networks to limit blast radius, and integrating mobile/IoT telemetry into existing monitoring and incident response workflows. With attacks increasingly targeting these devices, proactive governance can be the difference between a contained incident and a larger crisis.
Reference
Verizon. (2024). 2024 Mobile Security Index (MSI). Verizon.
Perplexity AI was employed in the research and development of this information.
Video: https://youtu.be/HbBIadarg60
Dr. Frank Kardasz, MPA, Ed.D.
May 3, 2026
Here is a guide, ironically mostly AI generated, to prompts researchers can use to help prevent AI from misquoting or fabricating reference sources:
AI language models generate text by predicting plausible patterns, not by retrieving verified facts. When asked for citations, they produce text that looks like legitimate academic references because they've seen similar patterns during training. This phenomenon — sometimes called "vibe citing" — affects an estimated 17–55% of AI-generated references. Prestigious conferences like NeurIPS 2025 have discovered over 100 hallucinated citations in accepted papers.[1][2]
Category 1: Guardrail Prompts (Forbid Fabrication)
These prompts set hard rules before the AI generates any content:[3]
· The Non-Invention Constraint:
"You must not generate any citation, reference, or source that is not verifiable. If you cannot find a source for a specific claim, state: 'I could not find a verifiable source for this specific claim.' Never invent a source."
· The Epistemic Accuracy System Prompt:
"You are a fact-conscious assistant. Your core principle is: 'If it is not verifiable, do not claim it.' Do not fabricate data, names, dates, events, studies, or quotes. Do not simulate sources or cite imaginary articles. When unsure, say: 'I don't know' or 'This cannot be confirmed.'"[4]
· The Boundary Constraint:
"Use only the sources I provide. If the answer isn't there, say: 'I could not find that in my knowledge sources.'"[5]
Category 2: Source-Grounded Prompts (Anchor AI to Real Text)
The most reliable strategy is to paste the actual source text into the prompt, forcing the AI to work only from what you provide:[6]
· The Context-Lock Prompt:
"Generate a synthesis based ONLY on these papers: [paste full abstract or text]. Do NOT invent citations. Do NOT cite papers not in this list. Include exact quotes with page numbers."[1]
· The Verbatim Excerpt Prompt:
"Extract a verbatim excerpt — not a
paraphrase — from the text I have pasted below that supports [claim]. If no
direct excerpt supports this claim, say so explicitly."[5]
(Note: Using the word
"verbatim" and asking for an "excerpt" rather than a
"quote" dramatically improves copy-paste accuracy, as
"quote" tends to invite paraphrase.)[5]
· The RTCF Structured Citation Prompt (Role–Task–Context–Format):
"You are an academic citation specialist [Role]. Generate a complete APA 7th edition citation [Task] for the following source: [paste all known bibliographic details — author, year, title, journal, DOI] [Context]. Output a single reference entry in APA 7th edition format [Format]."[6]
Category 3: Chain-of-Verification (CoVe) Prompts
This is a four-stage method developed by Meta researchers that forces the AI to self-check its own output independently before finalizing it:[7][8]
1. Stage 1 – Draft: Generate the initial claim or citation.
2. Stage 2 – Plan verification questions: "List the specific questions you would need to answer to verify each claim you just made."
3. Stage 3 – Answer independently: "Now answer each verification question independently, without referencing your earlier response."
4. Stage 4 – Reconcile: "Compare your verification answers to your original draft. Correct any claims that are not fully supported. If a citation cannot be verified, remove it."
A condensed single-prompt version of CoVe is:[3]
"First, generate the claim. Second, search your knowledge base for the supporting source. Third, compare the claim to the source. Fourth, only if verified, output the claim and citation. If unverified, omit."
Research confirms CoVe decreases hallucinations across list-based, closed-book, and long-form generation tasks.[8]
Category 4: Cross-Model Fact-Check Prompts
A practical technique is to pipe one AI's output into a second AI for verification:[9]
"Fact-check the following claim against its cited sources. For each source: (1) Confirm the URL is real and reachable; (2) Determine whether the source directly supports, contradicts, or is unrelated to the claim; (3) Spot any misrepresentation, selective quoting, or omitted context; (4) Give a verdict: well-supported, partially supported, unsupported, or contradicted."[9]
You can also use a follow-up verification prompt directly with the same AI:[6]
"For the citation you just gave me, is [Journal Name] a real peer-reviewed journal? What is its ISSN? Can you confirm that DOI [DOI number] leads to the article titled [Article Title]?"
Category 5: Structural Accountability Prompts
These prompts build traceability into the AI's output format:[10][5]
· Chunk-referencing prompt (useful when you provide a document):
"I have numbered my source text in chunks,, … For every claim you make, reference the chunk number you pulled it from in brackets."[11][12][9]
· Forced citation format prompt:
"Provide legal/factual statements ONLY with a citation in this format: [Author, Year, Title, DOI/URL, page number]. If you cannot supply all fields, do not include the claim."[10]
· Confidence-flagging prompt:
"For each claim, label it as: (A) Verified from provided text, (B) From general training knowledge — needs verification, or (C) Uncertain — do not use. Do not present (B) or (C) claims as established facts."[11]
|
Goal |
Prompt Keyword/Technique |
Source |
|
Prevent fabricated citations |
"Never invent a source" + honesty instruction |
|
|
Lock AI to provided text |
Paste source text + "based ONLY on these papers" |
|
|
Force verbatim quotes |
Use "verbatim" + ask for "excerpt" not "quote" |
|
|
Self-verification |
Chain-of-Verification (CoVe) 4-step prompt |
|
|
Cross-model checking |
Pipe output to second AI with fact-check prompt |
|
|
Structural traceability |
Numbered chunks + bracket referencing |
|
|
Confidence transparency |
Label claims A/B/C by verification status |
|
|
Citation format accuracy |
RTCF method (Role, Task, Context, Format) |
No prompt fully eliminates the risk. Even with all techniques applied, manual verification against the original source remains mandatory. Tools like Elicit, Consensus, Scite.ai, and Zotero are specifically designed for scholarly citation retrieval and validation and should be used alongside AI writing tools. The architecturally safest approach is Retrieval-Augmented Generation (RAG), which reduces hallucination rates by up to 71% by forcing the AI to generate only from pre-verified, retrieved documents.[12][13][2][14][15][9][1]
1. https://www.inra.ai/blog/citation-accuracy
2. https://www.youtube.com/watch?v=YtdIjpL-kB8
3. https://westoahu.hawaii.edu/distancelearning/tips/stop-hallucinating-3-prompts-that-make-ai-a-reliable-partner/
4. https://www.linkedin.com/posts/how-to-prompt_a-system-prompt-to-reduce-ai-hallucination-activity-7327636143884099584-jfFv
5. https://www.linkedin.com/posts/jamesbickerton_the-4-ai-prompts-that-finally-got-me-accurate-activity-7333484323947356162-mV_h
6. https://www.getpassionfruit.com/blog/blog-ai-prompt-engineering-citations
7. https://www.reddit.com/r/singularity/comments/16qcdsz/research_paper_meta_chainofverification_reduces/
8. https://arxiv.org/abs/2309.11495
9. https://www.reddit.com/r/PromptEngineering/comments/1m368sn/how_do_you_get_an_ai_to_actually_use_and_cite/
10. https://aiforlawyers.substack.com/p/top-ten-ways-to-eliminate-or-reduce
11. https://www.aiprompthackers.com/p/8-copy-paste-ai-prompts-to-stop-hallucinations
12. https://library.up.ac.za/c.php?g=1509323&p=11285631
13. https://libguides.brown.edu/c.php?g=1338928&p=9868287
14. https://www.itconvergence.com/blog/how-to-overcome-ai-hallucinations-using-retrieval-augmented-generation/
15. https://www.linkedin.com/posts/clevia-ai_ghost-citations-are-becoming-a-real-research-activity-7432091216625766400-UwDg
16. https://guides.lib.utexas.edu/AI/academic_integrity
17. https://library.fiu.edu/reportingthenews/plagiarism
18. https://www.pangram.com/blog/how-to-create-evidence-for-an-ai-detection-case
19. https://lib.guides.umd.edu/c.php?g=1340355&p=9896961
20. https://www.reddit.com/r/UniUK/comments/1hez1sj/how_can_universities_lecturers_tell_students_have/
21. https://arxiv.org/abs/2404.08189
22. https://arxiv.org/html/2509.05741v1
23. https://guides.lib.usf.edu/AI/promptengineering
24. https://arxiv.org/pdf/2403.01193.pdf
25. https://www.reddit.com/r/PromptEngineering/comments/1oczlny/building_a_fact_checker_prompt/
26. https://techcommunity.microsoft.com/blog/azure-ai-foundry-blog/best-practices-for-mitigating-hallucinations-in-large-language-models-llms/4403129
27. https://arxiv.org/abs/2405.00204
28. https://www.frontiersin.org/journals/artificial-intelligence/articles/10.3389/frai.2025.1658316/full
29. https://aws.amazon.com/blogs/machine-learning/detect-hallucinations-for-rag-based-systems/
Officer-involved shootings (OISs) are among the most scrutinized situations in policing, yet the officer’s own perception of what occurred is often incomplete or inaccurate, especially regarding the number of rounds fired. These discrepancies are frequently interpreted as evidence of deception, even though research shows they are a predictable consequence of neurophysiological stress responses, training artifacts, and trauma-related memory distortion.[1][2][3]
This article analyzes why an officer may state, “I only fired three rounds,” when forensic evidence establishes that many more rounds were discharged, and then explores implications for training, trauma, post-incident investigation, officer interrogation and counsel, legal ramifications, and defense strategies—including the use of case law and structured cross-examination both to challenge and to rehabilitate officer credibility.[4][2][5][1]
Research documents that officers in shootings experience intense physiological arousal accompanied by perceptual and memory distortions. Artwohl’s survey of 157 officers found that 84% reported diminished sound (auditory exclusion), 79% reported tunnel vision, 62% experienced time slowing, and 52% reported memory loss for part of the event, with 46% unable to recall some of their own behavior. Klinger’s interviews in 113 OISs similarly revealed high rates of auditory blunting, narrowed attentional focus, and fragmented recall.[2][5][1]
These distortions directly impair accurate round counting. Artwohl’s analysis of Klinger’s data found that 33% of officers could not accurately recall the number of rounds they fired, and that accuracy decreased sharply as the number of shots increased—from 81% accuracy with five or fewer rounds to 29% with six to nine rounds, and 0% when 13 or more rounds were fired. In other words, once a shooting escalates into a sustained volley, accurate self-report of round count becomes highly unlikely, even in lawful, objectively reasonable shootings.[1][2]
Case histories show that some officers fire their weapons yet have no conscious memory of doing so until confronted with physical or forensic evidence. Artwohl describes officers who:[1]
These patterns support the position that an officer’s statement—“I think I fired three rounds”—is best understood as a stress-influenced estimate rather than a deliberate falsehood. The combination of auditory exclusion, attentional narrowing, automatic motor responses, and trauma-related encoding deficits makes misestimation of rounds both expectable and scientifically explicable.[2][1]
Conventional firearms training tends to emphasize fixed, low round-count strings (for example, 2–3 rounds per drill) for ammunition conservation, time efficiency, and scoring simplicity. Officers become habituated to a schema in which handgun deployments are cognitively associated with small volleys of fire rather than sustained, threat-driven shooting.[3]
In many agencies:
When confronted with a real, rapidly evolving deadly-force encounter, the officer may fire until the threat stops, yet subsequent reconstruction of the event is filtered through the familiar, trained pattern of “a few rounds,” especially when memory is fragmented. Under stress, the brain fills gaps with plausible, training-based expectations; the result is a sincere but inaccurate estimate such as “two or three shots.”[2][3][1]
Standard live-fire range training differs from real shootings in several critical respects:
Stress-inoculation programs that attempt to simulate realistic threat levels (for example, force-on-force scenarios, complex “House of Horrors” drills) reveal that even in training, officers frequently misremember how many shots they fired or whether they fired at all. This indicates that performance under stress can be robust while contemporaneous self-monitoring remains imprecise.[2][1]
Investigators, prosecutors, and the public often expect officers to provide precise, linear narratives of shootings, including exact round counts and sequences. Yet cognitive science demonstrates that memory is reconstructive and vulnerable to fragmentation under stress; discrepancies between statements and physical evidence are not, by themselves, reliable indicators of deceit.[5][2][1]
Artwohl and others caution that officers who lack recall of all shots fired may be unfairly accused of lying or covering up, even when neurophysiological explanations are well-supported. Klinger’s findings that recall accuracy drops to 0% when 13 or more rounds are fired highlight the danger of equating misremembered round count with intentional falsehood. Investigators should integrate officer accounts with scene evidence, body-worn camera footage, and forensic analysis, viewing inconsistencies through the lens of stress-related memory distortion.[5][1][3]
Several scholars and professional bodies recommend delaying detailed, formal interviews of involved officers for at least 24 hours to allow for physiological recovery and memory consolidation, while still obtaining immediate public-safety information. Cognitive Interview techniques—open-ended prompts, context reinstatement, and multiple retrieval attempts—can facilitate more complete and accurate recall without suggestive questioning.[5][2][1]
Investigators should be trained in the normalcy of perceptual distortions and memory gaps in OISs and should avoid implying that any discrepancy equals deception. Agency policies that explicitly acknowledge these phenomena can assist in later litigation, demonstrating that such inconsistencies were anticipated and not automatically treated as misconduct.[2][1][3]
After a shooting, officers simultaneously function as key witnesses and potential criminal suspects. Best practices distinguish between narrowly tailored public-safety questions (for example, location of suspects, weapons, injured parties) and comprehensive criminal interrogation. Officers should provide necessary safety information but are generally advised to avoid detailed statements until they have consulted legal counsel.[7][5]
Many legal defense funds and professional associations recommend that officers:This approach is consistent with constitutional protections and recognizes that statements made under extreme stress may be inaccurate and later used for impeachment, even when not intentionally false.
Careful coordination between administrative and criminal processes helps protect both the integrity of the investigation and the officer’s constitutional rights.[7][5]
Fourth Amendment excessive-force analysis focuses on objective reasonableness, not on perfect recollection of every shot. In Plumhoff v. Rickard (2014), the U.S. Supreme Court held that officers did not violate the Fourth Amendment when they fired 15 shots to terminate a dangerous high-speed chase, emphasizing that reasonableness must be evaluated from the perspective of a reasonable officer on the scene and that multiple shots within a single rapidly evolving encounter do not transform an otherwise reasonable use of deadly force into a constitutional violation.[8][4]
Similarly, appellate courts have analyzed shootings involving multiple volleys by treating each volley as a distinct use of force, yet often extending qualified immunity where threats persisted and the time between volleys was short. In a Ninth Circuit decision summarized in 2024, an officer’s six shots were parsed into three separate uses of force, with the first two deemed reasonable as a matter of law and qualified immunity granted for the third volley as well, given the evolving threat and brief time intervals.[9]
Round count therefore matters, but primarily in relation to whether officers reassessed the threat as conditions changed; it is not, by itself, dispositive of reasonableness.An officer who states at the scene, “I think I fired three rounds,” when forensic evidence later shows 10 or more discharges, risks impeachment in both criminal and civil proceedings. Prosecutors or plaintiffs’ counsel may argue that:
In civil rights litigation under 42 U.S.C. § 1983, such inconsistencies may be framed as evidence of “tailored” testimony, especially when combined with other discrepancies. Administrative bodies may likewise treat inaccurate statements about round count as potential dishonesty, leading to discipline or termination even where the shooting itself is deemed lawful.[10][11][12]
At the same time, because research strongly supports the normalcy of memory distortion under extreme stress, defense counsel can argue that misstatements about rounds reflect trauma rather than deceit, especially when immediately qualified as estimates (for example, “I think,” “I believe”).[1][2][3]
Key cases that can inform training on multiple shots and officer recollection include:
In training, these cases can be used to show that: (a) courts expect officers to reassess as circumstances change, and (b) multiple shots alone do not equate to excessive force, but inaccurate statements about shots can damage credibility.
Defense attorneys should present peer‑reviewed research and professional literature to reframe round-count discrepancies as products of trauma and training, not moral failure. This includes:
Expert witnesses in police psychology, human factors, and use of force can explain to jurors that misestimating round count is consistent with well-established stress responses and does not indicate dishonesty.[2][1][3]
Defense counsel should also explore the officer’s firearms training, emphasizing:
By situating the misstatement within institutional training practices, counsel can argue that the discrepancy reflects systemic training limitations rather than individual deceit.
Effective defense strategy focuses on showing that, despite misestimation of rounds, the officer’s core narrative of the threat and justification for force remained consistent and is corroborated by independent evidence. Counsel can highlight that:
This approach aligns with Plumhoff and similar cases, where courts assess reasonableness based on the totality of circumstances rather than on perfect recollection of every shot.[4]
The following examples are designed for use in academy and in‑service training to illustrate how prosecutors or plaintiffs’ attorneys might attack an officer’s credibility over miscounted rounds—and how defense counsel and experts might respond.
Training discussion: Trainees can analyze how each question narrows the officer’s options, builds a theme of minimization, and uses ordinary expectations about memory to imply dishonesty. Trainers can then introduce the research on perceptual and memory distortions to discuss how an officer might honestly respond while acknowledging uncertainty.
Training discussion: Trainees can examine how these questions allow the officer to explain the context of the misstatement and emphasize honesty, while aligning their testimony with known phenomena like auditory exclusion and memory distortion.[2][1]