By Industry & Audience

How to Create Cybersecurity Awareness Videos From Policies and Real Scenarios

Turn security policies and safe simulations into actionable awareness videos with exact reporting paths, no fake hacker theater, and nine complete Golpo workflows.

Liam Park37 min read
A practical cybersecurity scenario showing phishing, a password manager, MFA, updates, and an incident-reporting path

The practical answer: Turn your security policy into training that shows employees exactly what to notice, where to report, and what happens next. Golpo is built to be the complete AI explainer workflow for that lesson. Start from the approved procedure, a locked script, or an authorized recording by your security lead. Golpo drafts the narration when you want a draft, plans the scenes, and renders the video after you review the script. You insert a sanitized picture of the real report control, keep the organization’s visual identity, and reuse the setup for the manager version.

The nine videos below are scenario briefs with finished renders. Example 1 is the employee-facing phishing lesson in Prompt Mode, with an illustrated report path. The internal version your team publishes uses Script Mode and your own sanitized interface. Examples 7–9 are hypothetical narration read by Golpo Audio Only. They demonstrate the format. They are not recordings of a security leader.

Who this is for

Security awareness and enablement leads preparing the next campaign or the next new-hire cohort. The artifact is two short lessons from one approved phishing procedure: an employee clip that shows notice, pause, report, and the next step, and a distinct manager clip for escalation.

What to set on a reporting video

ControlWhat changes for the reporting mistakePlan
Script ModeThe spoken reporting steps match the approved procedure. Visual directions stay in Video Instructions, so they are not read aloud. Prompt Mode can draft from the policy when you will approve the script first. About 1,050 characters fit in one selected minute.All plans. Length and controls vary. On Pay As You Go, Edit script before creating video bills 10% after the script and 90% after the video.
On-screen text from script onlyButton names and the report-channel label stay inside the approved script. Golpo may show a subset. This is not a caption track and it does not prove the procedure is current.Canvas and Sketch.
Custom ScenesGive notice, pause, report, and the next step their own scenes, within the engine limit. The map does not rewrite the narration.Growth and higher, and Pay As You Go.
Compact or ExpandedCompact keeps the suspicious message and the report control in one view. Expanded gives each action its own space. Notebook is Compact only.Color starts at Growth. In the API, an unsuffixed style value selects Compact, and _legacy selects Expanded on the ten pre-Notebook styles.
Own MediaInsert a sanitized screenshot or a safe recording of the real report button. A generated button is not evidence of your interface.Business and higher, and Pay As You Go.
Custom StyleSave the organization’s illustration style once, from an approved image, video, or description, and reuse it on the manager lesson. It follows the reference. Exact typography is something you check.Business and higher, and Pay As You Go. API use also needs API access.
Own Narration or AI PresenterAn authorized security-lead recording drives the visuals and sets duration and spoken language. A language setting does not translate that audio. Picture-in-Picture keeps the speaker visible. Or place a stock or custom presenter beside the lesson in a side-by-side or circle layout. A presenter is a generated performance, not a recording of the lead. Presenter API access is still described as coming soon.Own Narration: Business and higher, and Pay As You Go. Presenter: Creator and higher, and Pay As You Go.

From one phishing procedure to two lessons

Example 1, further down, is the published employee lesson: Prompt Mode, Professional Clean, 2 selected minutes, built from the NIST phishing note, with an illustrated inbox and report path. Use it to see the shape of the lesson. To publish internally, run the same job with your procedure and your button.

  1. Source. Attach the approved phishing procedure and the NIST or CISA page you use as background. In Script Mode, supply the employee steps: what to notice, when to pause, which control to use, and what the team does next.
  2. Settings. Select 2 minutes, horizontal. Map notice, pause, report, and next step with Custom Scenes. Insert the sanitized report button with Own Media. Select the organization’s Custom Style. Turn on on-screen text from the script. Choose the security lead’s recording, or a presenter that leaves the button visible.
  3. Script review. The security owner reads the narration before you render. Confirm the channel name matches the procedure.
  4. Result. You should have a short employee clip that shows the real control and the next step. Example 1 is the illustrated public version of that lesson.
  5. One correction. When the reporting UI changes, replace the button frame with frame editing if the spoken steps are still right. The first edited version is free across sessions until finalized. Later frame editing charges the selected duration, 2 credits on this standard 2-minute video, and it does not change the soundtrack. If the procedure’s words changed, revise the script and render again.
  6. One reuse. Write a distinct manager script for escalation: who is notified, what the manager does in the first hour, and what the manager leaves to the response team. Reuse the Custom Style. Keep the employee button out of the manager lesson unless the manager uses that same control. After both lessons are approved in the dashboard, the API can request the next role variant and return status. Your approval workflow stays outside Golpo. Scale includes API access. Business has a paid API add-on. API Only is separate metering and does not include dashboard generation. See the API docs.

Optional: research a public awareness series

Internal training starts from your policy. Use this worksheet only if you also publish a public series. Do not ask ChatGPT or Claude, “What niche is profitable?” and publish the first list. Use AI to organize evidence you collect from YouTube search, audience comments, official sources, and your own expertise. The niche must produce repeatable viewer questions without forcing you to manufacture certainty.

Copyable niche-research prompt for ChatGPT or Claude

I am evaluating a YouTube channel about cybersecurity awareness and policy training.
My expertise or access: [be specific].
My intended audience: [one group].
My geography/jurisdiction: [if relevant].

Do not claim current search demand from memory. First give me a research worksheet for:
1. 30 real YouTube search results and their publish dates, views, formats, and unanswered comments;
2. 20 recurring audience questions from comments, forums, support logs, or classrooms;
3. authoritative primary sources available for each question;
4. update frequency, rights, safety, and qualified-review burden;
5. a 20-video pilot with one learning outcome per episode.

Then score three channel angles from 1–5 on evidence access, visual explainability,
repeatability, freshness burden, harm if wrong, and my unfair advantage.
Flag every conclusion that still needs live research.

Run the research yourself. Reject an angle if its best titles require guaranteed outcomes, private data, unlicensed media, fake quotations, diagnosis, unsafe imitation, or advice beyond your competence. Use the faceless niche scorecard for a deeper commercial and editorial test.

Choose the correct Golpo input mode

ModeUse it whenYou supplyMain failure to prevent
Prompt ModeThe generator may organize wording inside a narrow, source-controlled brief.Audience, outcome, approved facts, source URL, visual sequence, prohibitions, CTA.The prompt becomes an idea only, so the model fills gaps with plausible fiction.
Script ModeEvery spoken word, qualification, number, or quotation must stay fixed.A complete narration within the current per-minute character allowance, plus separate visual direction.Shot directions are pasted into narration and spoken aloud.
Own NarrationThe real speaker’s voice, authority, testimony, pronunciation, or delivery matters.A clean recording you have rights to use, plus visual direction. Duration follows the audio.A creator expects Voice Instructions or voice selection to change uploaded audio.

Important: Prompt/Script text belongs in the main input. Video Instructions control visual sequence, diagrams, continuity, exclusions, and on-screen implications. Voice Instructions control synthetic narration pace and delivery. With Own Narration, the recording replaces voice selection and Voice Instructions.

The source-to-video workflow

  1. Write the one-sentence outcome: by the end, the employee can notice the signal, use the approved report path, and say what happens next.
  2. Build a claim sheet: claim, source, as-of date, exact supporting passage or data, limitation, rights status, and update trigger.
  3. Choose the mode: Prompt for bounded synthesis, Script for exact language, Own Narration for a real speaker.
  4. Write narration separately from production direction: no camera cues or bracketed scene notes in a Script Mode narration.
  5. Write Video Instructions: define the visual sequence, recurring anchors, labels, scale, forbidden imagery, accessibility, and final CTA.
  6. Write Voice Instructions: specify pace, tone, pauses, and pronunciations only when using a synthetic voice.
  7. Generate and edit: review the script before generation; inspect every frame and revise misleading visuals.
  8. Run two approvals: a subject-matter review for claims and a production review for what the final video implies.
  9. Publish the evidence trail: source links, access dates, disclosures, captions, corrections route, and update owner.

Nine end-to-end cybersecurity awareness and policy training examples

These are complete production briefs. Examples 1–3 use Prompt Mode. Examples 4–6 use Script Mode and are the pattern for approved reporting language. Examples 7–9 occupy the Own Narration slot with hypothetical scripts: Golpo Audio Only read the words below. They are demonstration narration, not a security leader’s recording. The report buttons in these renders are illustrated. For an internal publish, insert a sanitized capture of your control with Own Media, and use a recording you have permission to publish or an AI Presenter beside the lesson.

Prompt Mode: Golpo writes from a bounded brief

Prompt Mode example 1 of 3

1. Spot and report a phishing message

Finished Golpo video · Example 1 · Prompt Mode · open MP4

Audience: all employees
Learning result: Teach the organization’s exact reporting action.
Authority source: NIST: Recognizing and Reporting Phishing

Exact Golpo configuration

Own Narration: OFF · Script Mode: OFF · Duration: 2 minutes · Orientation: Horizontal (16:9) · Style: Professional Clean · Color: ON · Language: English · Voice: Female 1 · Pace: Normal · Music: None · Edit script before generation: ON

Exact prompt used to create this video

This is the exact prompt sent to Golpo Prompt Mode for the rendered example. Copy it, then replace the audience, source, approved facts, and accuracy boundary for your topic.

Create a 2 minutes illustrated explainer for all employees.

Title: Spot and report a phishing message
Learning goal: Teach the organization’s exact reporting action.
Primary source: NIST: Recognizing and Reporting Phishing — https://www.nist.gov/blogs/cybersecurity-insights/cybersecurity-awareness-month-2022-recognizing-reporting-phishing
Approved facts: Unexpected requests, out-of-character messages, urgency, credential requests, and gift-card demands are reasons to pause and verify through a known channel.

Structure:
1. Open with one precise question, not hype.
2. Orient the viewer with the minimum definitions needed.
3. Explain the mechanism in three visual steps.
4. Correct one likely misconception.
5. End with this action: End on the company’s approved report method.

Visual sequence: Fictional inbox → three signals → pause → verify via known contact → report button/path → security team receives.
Accuracy boundary: Use no real credentials, active malicious link, or universal claim that one signal proves phishing.
Do not invent numbers, quotations, studies, dates, products, people, or causal claims. If a detail is not in the approved facts, omit it.

Video Instructions

Use one continuous visual system: Fictional inbox → three signals → pause → verify via known contact → report button/path → security team receives. Keep recurring people, objects, colors, and spatial positions consistent. Put no unsupported numbers or quotations on screen. Use no real credentials, active malicious link, or universal claim that one signal proves phishing. Use large readable labels, high contrast, and captions. Do not show brand logos unless supplied and cleared. End on the stated CTA, not a generic subscribe animation.

Voice Instructions

Speak at a normal pace with calm authority. Use plain language, pause briefly before the misconception or safety boundary, and never sound excited about risk, diagnosis, guaranteed outcomes, or fear. Pronounce specialist terms from the reviewer-approved pronunciation list.

YouTube package

  • Search-led title: Spot and report a phishing message — Explained Visually
  • Thumbnail: PAUSE. VERIFY. REPORT.
  • CTA: End on the company’s approved report method.

Review before publish

Open the cited source again. Check every spoken and on-screen claim, unit, date, label, and implied relationship. Confirm that the final frame obeys this boundary: Use no real credentials, active malicious link, or universal claim that one signal proves phishing. Add the source and its access date to the description.

Prompt Mode example 2 of 3

2. Why MFA helps

Finished Golpo video · Example 2 · Prompt Mode · open MP4

Audience: employees and customers
Learning result: Explain factors and the enrollment path without revealing live screens.
Authority source: CISA: Require Multifactor Authentication

Exact Golpo configuration

Own Narration: OFF · Script Mode: OFF · Duration: 2 minutes · Orientation: Horizontal (16:9) · Style: Professional Clean · Color: ON · Language: English · Voice: Female 1 · Pace: Normal · Music: None · Edit script before generation: ON

Exact prompt used to create this video

This is the exact prompt sent to Golpo Prompt Mode for the rendered example. Copy it, then replace the audience, source, approved facts, and accuracy boundary for your topic.

Create a 2 minutes illustrated explainer for employees and customers.

Title: Why MFA helps
Learning goal: Explain factors and the enrollment path without revealing live screens.
Primary source: CISA: Require Multifactor Authentication — https://www.cisa.gov/audiences/small-and-medium-businesses/secure-your-business/require-multifactor-authentication
Approved facts: MFA requires more than one factor and can reduce account risk when a password is compromised; phishing-resistant methods provide stronger protection where available.

Structure:
1. Open with one precise question, not hype.
2. Orient the viewer with the minimum definitions needed.
3. Explain the mechanism in three visual steps.
4. Correct one likely misconception.
5. End with this action: Link the organization’s official setup page.

Visual sequence: Password-only door → second factor → attacker with password blocked → approved enrollment checklist.
Accuracy boundary: Do not claim MFA makes an account impossible to compromise or display real recovery codes.
Do not invent numbers, quotations, studies, dates, products, people, or causal claims. If a detail is not in the approved facts, omit it.

Video Instructions

Use one continuous visual system: Password-only door → second factor → attacker with password blocked → approved enrollment checklist. Keep recurring people, objects, colors, and spatial positions consistent. Put no unsupported numbers or quotations on screen. Do not claim MFA makes an account impossible to compromise or display real recovery codes. Use large readable labels, high contrast, and captions. Do not show brand logos unless supplied and cleared. End on the stated CTA, not a generic subscribe animation.

Voice Instructions

Speak at a normal pace with calm authority. Use plain language, pause briefly before the misconception or safety boundary, and never sound excited about risk, diagnosis, guaranteed outcomes, or fear. Pronounce specialist terms from the reviewer-approved pronunciation list.

YouTube package

  • Search-led title: Why MFA helps — Explained Visually
  • Thumbnail: A PASSWORD IS ONE LOCK
  • CTA: Link the organization’s official setup page.

Review before publish

Open the cited source again. Check every spoken and on-screen claim, unit, date, label, and implied relationship. Confirm that the final frame obeys this boundary: Do not claim MFA makes an account impossible to compromise or display real recovery codes. Add the source and its access date to the description.

Prompt Mode example 3 of 3

3. Why software updates matter

Finished Golpo video · Example 3 · Prompt Mode · open MP4

Audience: small-business staff
Learning result: Make restart and update behavior concrete.
Authority source: CISA small-business resources

Exact Golpo configuration

Own Narration: OFF · Script Mode: OFF · Duration: 2 minutes · Orientation: Horizontal (16:9) · Style: Professional Clean · Color: ON · Language: English · Voice: Female 1 · Pace: Normal · Music: None · Edit script before generation: ON

Exact prompt used to create this video

This is the exact prompt sent to Golpo Prompt Mode for the rendered example. Copy it, then replace the audience, source, approved facts, and accuracy boundary for your topic.

Create a 2 minutes illustrated explainer for small-business staff.

Title: Why software updates matter
Learning goal: Make restart and update behavior concrete.
Primary source: CISA small-business resources — https://www.cisa.gov/small-and-medium-sized-business-resources
Approved facts: Updates can patch known vulnerabilities; organizations should use supported software and an approved update process.

Structure:
1. Open with one precise question, not hype.
2. Orient the viewer with the minimum definitions needed.
3. Explain the mechanism in three visual steps.
4. Correct one likely misconception.
5. End with this action: Tell viewers where to report a failed update.

Visual sequence: Known flaw → vendor patch → approved deployment → restart → confirmation; show exception route for managed devices.
Accuracy boundary: Do not tell employees to bypass IT controls or install unapproved software.
Do not invent numbers, quotations, studies, dates, products, people, or causal claims. If a detail is not in the approved facts, omit it.

Video Instructions

Use one continuous visual system: Known flaw → vendor patch → approved deployment → restart → confirmation; show exception route for managed devices. Keep recurring people, objects, colors, and spatial positions consistent. Put no unsupported numbers or quotations on screen. Do not tell employees to bypass IT controls or install unapproved software. Use large readable labels, high contrast, and captions. Do not show brand logos unless supplied and cleared. End on the stated CTA, not a generic subscribe animation.

Voice Instructions

Speak at a normal pace with calm authority. Use plain language, pause briefly before the misconception or safety boundary, and never sound excited about risk, diagnosis, guaranteed outcomes, or fear. Pronounce specialist terms from the reviewer-approved pronunciation list.

YouTube package

  • Search-led title: Why software updates matter — Explained Visually
  • Thumbnail: THE PATCH ONLY WORKS IF INSTALLED
  • CTA: Tell viewers where to report a failed update.

Review before publish

Open the cited source again. Check every spoken and on-screen claim, unit, date, label, and implied relationship. Confirm that the final frame obeys this boundary: Do not tell employees to bypass IT controls or install unapproved software. Add the source and its access date to the description.

Script Mode: you lock every spoken word

Script Mode example 1 of 3

4. Use a password manager

Finished Golpo video · Example 4 · Script Mode · open MP4

Audience: general workforce
Learning result: Explain the behavior change, not a brand ranking.
Authority source: CISA small-business resources

Exact Golpo configuration

Own Narration: OFF · Script Mode: ON · Duration: 2 minutes · Orientation: Horizontal (16:9) · Style: Professional Clean · Color: ON · Language: English · Voice: Female 1 · Pace: Normal · Music: None · Edit script before generation: ON

Exact script used to create this video

This is the exact Script Mode narration supplied to Golpo. Golpo was instructed to preserve these spoken words while creating the visuals.

Reusing one password across accounts turns one exposed password into several risks. An approved password manager can generate and store a different strong password for each account, so you do not have to memorize them all. Protect the manager itself with the authentication and recovery process your organization approves. Never place a master password or recovery code in a shared document, ticket, or training demo. If you cannot access the approved tool, contact the support route shown at the end of this video.

Video Instructions

Use one continuous visual system: One reused password → breach spread → unique generated passwords in vault → MFA on vault → recovery plan. Keep recurring people, objects, colors, and spatial positions consistent. Put no unsupported numbers or quotations on screen. Never show a real vault, master password, recovery key, or credential. Use large readable labels, high contrast, and captions. Do not show brand logos unless supplied and cleared. End on the stated CTA, not a generic subscribe animation.

Voice Instructions

Speak at a normal pace with calm authority. Use plain language, pause briefly before the misconception or safety boundary, and never sound excited about risk, diagnosis, guaranteed outcomes, or fear. Pronounce specialist terms from the reviewer-approved pronunciation list.

YouTube package

  • Search-led title: Use a password manager — Explained Visually
  • Thumbnail: ONE BREACH, MANY ACCOUNTS?
  • CTA: Link the approved password-manager setup guide.

Review before publish

Open the cited source again. Check every spoken and on-screen claim, unit, date, label, and implied relationship. Confirm that the final frame obeys this boundary: Never show a real vault, master password, recovery key, or credential. Add the source and its access date to the description.

Script Mode example 2 of 3

5. Report an incident before investigating it yourself

Finished Golpo video · Example 5 · Script Mode · open MP4

Audience: employees
Learning result: Replace fear of blame with one clear action path.
Authority source: NIST incident-response resources

Exact Golpo configuration

Own Narration: OFF · Script Mode: ON · Duration: 2 minutes · Orientation: Horizontal (16:9) · Style: Professional Clean · Color: ON · Language: English · Voice: Female 1 · Pace: Normal · Music: None · Edit script before generation: ON

Exact script used to create this video

This is the exact Script Mode narration supplied to Golpo. Golpo was instructed to preserve these spoken words while creating the visuals.

If something seems wrong, report it through the approved security channel as soon as you can. Include what you observed, when it happened, which device or account was involved, and any action you already took. Do not delete messages, wipe a device, contact an attacker, or run unapproved tools unless your organization’s incident playbook tells you to. A quick report is not an admission of fault. It gives the response team time and evidence to decide what happens next.

Video Instructions

Use one continuous visual system: Suspicious event → disconnect only if policy says → capture basic facts → approved report channel → response team takes over. Keep recurring people, objects, colors, and spatial positions consistent. Put no unsupported numbers or quotations on screen. Company security owner must supply exact steps; never publish internal phone numbers on a public page. Use large readable labels, high contrast, and captions. Do not show brand logos unless supplied and cleared. End on the stated CTA, not a generic subscribe animation.

Voice Instructions

Speak at a normal pace with calm authority. Use plain language, pause briefly before the misconception or safety boundary, and never sound excited about risk, diagnosis, guaranteed outcomes, or fear. Pronounce specialist terms from the reviewer-approved pronunciation list.

YouTube package

  • Search-led title: Report an incident before investigating it yourself — Explained Visually
  • Thumbnail: REPORT FIRST—DON'T HIDE IT
  • CTA: End with the tested internal route and backup route.

Review before publish

Open the cited source again. Check every spoken and on-screen claim, unit, date, label, and implied relationship. Confirm that the final frame obeys this boundary: Company security owner must supply exact steps; never publish internal phone numbers on a public page. Add the source and its access date to the description.

Script Mode example 3 of 3

6. Backups only help if recovery is tested

Finished Golpo video · Example 6 · Script Mode · open MP4

Audience: small-business owners
Learning result: Show backup as a recovery process, not a checkmark.
Authority source: CISA small-business resources

Exact Golpo configuration

Own Narration: OFF · Script Mode: ON · Duration: 2 minutes · Orientation: Horizontal (16:9) · Style: Professional Clean · Color: ON · Language: English · Voice: Female 1 · Pace: Normal · Music: None · Edit script before generation: ON

Exact script used to create this video

This is the exact Script Mode narration supplied to Golpo. Golpo was instructed to preserve these spoken words while creating the visuals.

A backup is useful only if the organization can restore the data it needs. Start by identifying which systems and files are critical. Create copies on the approved schedule, protect them from the same failure or account compromise, and monitor whether jobs complete. Then run a controlled restore test and record how long recovery took and what was missing. The right design depends on your systems, risk, and legal obligations, so involve qualified IT and security owners.

Video Instructions

Use one continuous visual system: Critical data → scheduled copies → separated storage → restore test → recovery time note → owner review. Keep recurring people, objects, colors, and spatial positions consistent. Put no unsupported numbers or quotations on screen. Do not prescribe architecture or claim any backup is ransomware-proof. Use large readable labels, high contrast, and captions. Do not show brand logos unless supplied and cleared. End on the stated CTA, not a generic subscribe animation.

Voice Instructions

Speak at a normal pace with calm authority. Use plain language, pause briefly before the misconception or safety boundary, and never sound excited about risk, diagnosis, guaranteed outcomes, or fear. Pronounce specialist terms from the reviewer-approved pronunciation list.

YouTube package

  • Search-led title: Backups only help if recovery is tested — Explained Visually
  • Thumbnail: CAN YOU RESTORE IT?
  • CTA: Ask the owner to schedule one restore test with IT.

Review before publish

Open the cited source again. Check every spoken and on-screen claim, unit, date, label, and implied relationship. Confirm that the final frame obeys this boundary: Do not prescribe architecture or claim any backup is ransomware-proof. Add the source and its access date to the description.

Own Narration: your recording controls delivery

Own Narration example 1 of 3

7. Your security lead explains the report button

Finished Golpo video · Example 7 · Own Narration Mode · open MP4

Playable source audio used for this video

Golpo Audio Only · exact transcript verified · open or download MP3

Exact Golpo audio-only settings
Audio Only: ON · Timing: automatic · Language: English · Voice: Warm neutral female (solo-female-3)

Prompt: Create a natural audio-only narration titled: Your security lead explains the report button. Read the supplied script exactly.

Voice Instructions: Sound like a thoughtful person explaining a real experience to one listener. Use natural conversational phrasing, varied but restrained intonation, and brief pauses between ideas. Keep a warm neutral tone. Do not sound like an announcer, advertisement, synthetic assistant, or podcast intro. Read only the supplied script, without adding an introduction, sign-off, or Golpo tagline.

Audience: company employees
Learning result: Show one report path and what the team does after the report.
Authority source: NIST incident-response resources. Swap in your approved incident playbook for an internal publish.
Demonstration label: The voice is Golpo Audio Only reading a hypothetical script. It is not a security lead. The button on screen is illustrated.

Exact Golpo configuration

Own Narration: ON · Upload: reviewed MP3/WAV · Script Mode: OFF · Duration: automatic from audio · Orientation: Horizontal (16:9) · Style: Professional Clean · Color: ON · Music: None · Spoken language: match recording · Voice selection: not used · Voice Instructions: not used

Two-step Golpo workflow: first create or record a clean MP3/WAV. The playable demo audio above was made with Golpo Audio Only from the exact transcript below. Then turn Own Narration ON, upload the audio, and let its duration control the video. During the video step, Golpo follows the uploaded file rather than the video voice selector.

Exact narration transcript used for this video

The playable MP3 above speaks this exact transcript. To use your own voice instead, record the same kind of reviewed narration and upload that file with Own Narration ON.

I lead our security response team. If you receive a suspicious email, use the Report Phishing button shown here. If that button is unavailable, open the help portal and choose Security Incident. Include the time, sender, and what you clicked or entered. Do not forward the message to coworkers. Once submitted, our team reviews the report and contacts you if we need more information. Reporting quickly helps us protect everyone, and you will not be blamed for raising a concern in good faith.

Video Instructions

Use one continuous visual system: Fictional suspicious email → cursor over approved report button → confirmation → what happens next → backup phone/channel. Keep recurring people, objects, colors, and spatial positions consistent. Put no unsupported numbers or quotations on screen. Record in a sandbox; redact internal-sensitive details in public versions. Use large readable labels, high contrast, and captions. Do not show brand logos unless supplied and cleared. End on the stated CTA, not a generic subscribe animation.

Voice Instructions

Not used. Golpo follows the uploaded narration. Record in a quiet room, keep a steady distance from the microphone, leave a short pause between sections, and do not upload a voice you lack permission to publish.

YouTube package

  • Search-led title: Your security lead explains the report button — Explained Visually
  • Thumbnail: HERE'S EXACTLY WHERE TO REPORT
  • CTA: Ask employees to locate—not click—the route during training.

Review before publish

Open the cited source again. Check every spoken and on-screen claim, unit, date, label, and implied relationship. Confirm that the final frame obeys this boundary: Record in a sandbox; redact internal-sensitive details in public versions. Add the source and its access date to the description.

Own Narration example 2 of 3

8. Narrate a tabletop scenario

Finished Golpo video · Example 8 · Own Narration Mode · open MP4

Playable source audio used for this video

Golpo Audio Only · exact transcript verified · open or download MP3

Exact Golpo audio-only settings
Audio Only: ON · Timing: automatic · Language: English · Voice: Calm authoritative male (solo-male-3)

Prompt: Create a natural audio-only narration titled: Narrate a tabletop scenario. Read the supplied script exactly.

Voice Instructions: Sound like a thoughtful person explaining a real experience to one listener. Use natural conversational phrasing, varied but restrained intonation, and brief pauses between ideas. Keep a warm neutral tone. Do not sound like an announcer, advertisement, synthetic assistant, or podcast intro. Read only the supplied script, without adding an introduction, sign-off, or Golpo tagline.

Audience: managers and incident coordinators
Learning result: Turn a dry exercise into a decision timeline.
Authority source: CISA tabletop exercise fact sheet (PDF). Substitute your own tabletop plan after legal review.
Demonstration label: The voice is Golpo Audio Only. The scenario in the script is hypothetical.

Exact Golpo configuration

Own Narration: ON · Upload: reviewed MP3/WAV · Script Mode: OFF · Duration: automatic from audio · Orientation: Horizontal (16:9) · Style: Professional Clean · Color: ON · Music: None · Spoken language: match recording · Voice selection: not used · Voice Instructions: not used

Two-step Golpo workflow: first create or record a clean MP3/WAV. The playable demo audio above was made with Golpo Audio Only from the exact transcript below. Then turn Own Narration ON, upload the audio, and let its duration control the video. During the video step, Golpo follows the uploaded file rather than the video voice selector.

Exact narration transcript used for this video

The playable MP3 above speaks this exact transcript. To use your own voice instead, record the same kind of reviewed narration and upload that file with Own Narration ON.

This is a fictional tabletop exercise. At 9:10, our support team receives several reports of inaccessible files. The first question is not who to blame; it is who has authority to declare an incident and which channel remains trusted. At 9:20, a supplier also reports an outage. We record each decision, assumption, and missing contact. The exercise does not prove we would succeed in a real incident. Its purpose is to assign owners and dates to the gaps we find.

Video Instructions

Use one continuous visual system: Scenario inject → decision owner → communication fork → dependency → gap log → action owner/date. Keep recurring people, objects, colors, and spatial positions consistent. Put no unsupported numbers or quotations on screen. Use fictional systems and data; do not expose exploitable details. Use large readable labels, high contrast, and captions. Do not show brand logos unless supplied and cleared. End on the stated CTA, not a generic subscribe animation.

Voice Instructions

Not used. Golpo follows the uploaded narration. Record in a quiet room, keep a steady distance from the microphone, leave a short pause between sections, and do not upload a voice you lack permission to publish.

YouTube package

  • Search-led title: Narrate a tabletop scenario — Explained Visually
  • Thumbnail: WHO DECIDES IN THE FIRST HOUR?
  • CTA: Publish only the lessons approved for the audience.

Review before publish

Open the cited source again. Check every spoken and on-screen claim, unit, date, label, and implied relationship. Confirm that the final frame obeys this boundary: Use fictional systems and data; do not expose exploitable details. Add the source and its access date to the description.

Own Narration example 3 of 3

9. A safe demo of a fake login page

Finished Golpo video · Example 9 · Own Narration Mode · open MP4

Playable source audio used for this video

Golpo Audio Only · exact transcript verified · open or download MP3

Exact Golpo audio-only settings
Audio Only: ON · Timing: automatic · Language: English · Voice: Warm neutral female (solo-female-3)

Prompt: Create a natural audio-only narration titled: A safe demo of a fake login page. Read the supplied script exactly.

Voice Instructions: Sound like a thoughtful person explaining a real experience to one listener. Use natural conversational phrasing, varied but restrained intonation, and brief pauses between ideas. Keep a warm neutral tone. Do not sound like an announcer, advertisement, synthetic assistant, or podcast intro. Read only the supplied script, without adding an introduction, sign-off, or Golpo tagline.

Audience: security-awareness learners
Learning result: Show realistic signals without creating a reusable attack kit.
Authority source: CISA: Recognize and Report Phishing. Use your lab environment only under the security owner’s rules.
Demonstration label: The voice is Golpo Audio Only reading a hypothetical training script.

Exact Golpo configuration

Own Narration: ON · Upload: reviewed MP3/WAV · Script Mode: OFF · Duration: automatic from audio · Orientation: Horizontal (16:9) · Style: Professional Clean · Color: ON · Music: None · Spoken language: match recording · Voice selection: not used · Voice Instructions: not used

Two-step Golpo workflow: first create or record a clean MP3/WAV. The playable demo audio above was made with Golpo Audio Only from the exact transcript below. Then turn Own Narration ON, upload the audio, and let its duration control the video. During the video step, Golpo follows the uploaded file rather than the video voice selector.

Exact narration transcript used for this video

The playable MP3 above speaks this exact transcript. To use your own voice instead, record the same kind of reviewed narration and upload that file with Own Narration ON.

This page is a training simulation and does not collect credentials. Notice that the message creates urgency and the link destination does not match the service we expect. My password manager also does not recognize the page, which is a warning—not final proof. I close the page, navigate through the organization’s known bookmark, and report the original message. Do not test suspicious sites yourself on a work device. Follow your organization’s reporting procedure.

Video Instructions

Use one continuous visual system: Clearly labeled simulation → suspicious URL shape → password-manager mismatch → independent navigation → report. Keep recurring people, objects, colors, and spatial positions consistent. Put no unsupported numbers or quotations on screen. Never host a credential harvester, show real domains, or ask learners to enter credentials. Use large readable labels, high contrast, and captions. Do not show brand logos unless supplied and cleared. End on the stated CTA, not a generic subscribe animation.

Voice Instructions

Not used. Golpo follows the uploaded narration. Record in a quiet room, keep a steady distance from the microphone, leave a short pause between sections, and do not upload a voice you lack permission to publish.

YouTube package

  • Search-led title: A safe demo of a fake login page — Explained Visually
  • Thumbnail: THIS PAGE IS A SIMULATION
  • CTA: Link the official reporting route after the simulation.

Review before publish

Open the cited source again. Check every spoken and on-screen claim, unit, date, label, and implied relationship. Confirm that the final frame obeys this boundary: Never host a credential harvester, show real domains, or ask learners to enter credentials. Add the source and its access date to the description.

SEO that earns the click without breaking trust

  • Title: lead with the exact viewer question and a concrete mechanism: “How X Works,” “Why X Happens,” or “X Checklist.” Do not use “guaranteed,” “secret,” or “everything” unless literally supportable.
  • Thumbnail: show one tension or misconception in three to five words. The examples above include a tested starting phrase.
  • Description: answer the question in the first two lines, then list sources, as-of date, audience boundary, disclosure, chapters, and corrections contact.
  • Chapters: name the actual learning steps rather than “Intro” and “More.”
  • Series links: send viewers to the next prerequisite or application, not a random popular upload.

YouTube’s monetization policies require original, authentic content and can reject repetitive or mass-produced templates. Add your own research, teaching decision, case, analysis, narration, or demonstration. If realistic synthetic or altered content could mislead a viewer, review YouTube’s current altered and synthetic content disclosure guidance.

Final quality-control checklist

  • One audience, one reporting action, and a security owner for the wording.
  • The script matches the current procedure. On-screen labels come from that script.
  • The report control is a sanitized capture, or the lesson is marked as the illustrated public example.
  • Credentials, live malicious links, and exploitable internal detail stay out of the upload.
  • Prompt, Script, or Own Narration is chosen for a stated reason, and Video Instructions are not spoken aloud.
  • Rights and consent are cleared for audio, images, and the security lead’s voice or photo.
  • Captions are reviewed, and color is not the only carrier of meaning.
  • The LMS, the quiz, and the completion record stay in your learning system.
  • A named owner refreshes the lesson when the reporting UI changes.

Authority sources used in these examples

Trend-led Golpo creator guide series

These guides answer the strongest recurring production needs seen across current user videos. Use adjacent guides for formats that overlap your channel.

  1. Start a Faceless YouTube Channel With Golpo
  2. Financial Education Videos With AI
  3. History Explainer Videos With AI
  4. Science and Engineering Explainers With AI
  5. Psychology and Self-Improvement Videos With AI
  6. Health and Patient-Education Videos With AI
  7. Educational Videos for Kids With AI
  8. Cybersecurity Awareness Videos With AI (this guide)
  9. Sermons and Study Notes to Illustrated Videos
  10. Home-Service Customer Education Videos With AI

FAQ

Can Golpo create cybersecurity awareness and policy training videos?

Golpo can turn an approved policy, a script, or an authorized recording into an illustrated video. The security owner still approves the reporting steps. The video is not an interactive phishing simulation, and it does not replace the LMS.

When should reporting instructions use Script Mode?

Use Script Mode when the spoken reporting steps must match the approved procedure. Put visual directions in Video Instructions. Prompt Mode can draft from the policy when you will review the script before rendering. About 1,050 characters of narration fit in one selected minute.

How do I show our real report button?

Insert a sanitized screenshot or a safe recording of the button with Own Media. A generated picture of a button is not evidence of your interface. Own Media is on Business and higher and on Pay As You Go.

Are the security-lead videos on this page a real person's recording?

Examples 7–9 use Golpo Audio Only to read a written script. They are hypothetical demonstration narration. For an internal video, record an authorized security lead with Own Narration, or place an AI Presenter beside the explainer. A presenter is a generated performance, not that person.

What is the difference between Video Instructions and Voice Instructions?

Video Instructions specify what viewers see: sequence, diagrams, labels, prohibited imagery, and continuity. Voice Instructions specify how a selected synthetic voice speaks. They do not change an uploaded narration.

Which Golpo plan do I need for an internal reporting video?

Examples 1–6 select 2 minutes, which is 2 credits on a standard render. Custom Scenes start at Growth and on Pay As You Go. Own Media, Custom Style and Own Narration are on Business and higher and on Pay As You Go. Frame editing: all paid plans. See the pricing page.

Fix one reporting mistake before the next cohort

Before the next awareness campaign or new-hire cohort, take one recurring reporting mistake and turn the approved procedure into the employee clip, with the sanitized button and a manager escalation lesson beside it. The security owner signs off on the final video.

Create the reporting video · See Business and Pay As You Go