Internal activity may bypass the gateway
Peer traffic may not cross the gateway Firewall. Internal segmentation, permissions and endpoint visibility are needed.
Understand network and endpoint protection, then practise payment, account and file-risk awareness. Free learning for Hong Kong businesses; no sign-in required.
In the age of AI-enabled scams, encryption is only part of the picture. Know who you are dealing with.
A Firewall controls traffic that passes through it. EDR observes activity on computers to support investigation and response. Explore the two layers using a GDMME rack and Huorong enterprise endpoint security as examples.
Select a setup below to compare protection layers
Select a scenario to see how the threat unfolds
The animation repeats continuously. Selecting a setup, scenario or step keeps it playing. Replay starts the sequence again.
Alt +Enter Full screenEsc ExitHover over or focus within this lesson to use the shortcut.
The diagram keeps a readable scale. Scroll sideways within it to see the computers, or focus the diagram and use the arrow keys.
Red, orange and green indicate the configured layers, not security ratings or live status. Both layers do not guarantee protection against every attack. Actual capabilities and outcomes depend on product edition, licensing, rules, updates and ongoing management. Reachability, alerts and successful compromise are different states.
Peer traffic may not cross the gateway Firewall. Internal segmentation, permissions and endpoint visibility are needed.
Attachments or cloud services can arrive over allowed connections. Gateway rules alone do not establish file safety.
Mistakes, stolen accounts and improper sharing also need least privilege, auditing and data protection.
This example assumes a matching deny rule is configured. The Firewall rejects the connection at the gateway.
Endpoint agents remain available to observe host activity. This example connection was already denied at the gateway.
Assess capabilities as well as labels. Antivirus includes identifying and handling malicious files. EDR focuses on endpoint detection, investigation and response. Huorong is an enterprise endpoint-security example here; full EDR, event history and isolation capabilities must be confirmed for the edition, licence and proposal.
Yes. Rules, updates, alert follow-up and asset scope need ongoing management, alongside account protection, backups and staff reporting.
Huorong Enterprise is provided by distributor AL-TOUCH SOLUTIONS LIMITED 一大方案有限公司. Discuss licensing, control centre deployment, endpoint policies and ongoing management alongside GDMME network protection.
Review protection across office computers and important servers, distribute policies and follow up improvements centrally.
From how attacks begin to how to limit their impact. Choose a scenario and practise your next step.
A ransom message appears on your computer and several shared files will not open. A colleague has the same problem, and the backup drive is on your desk.
Do not rush to restart or connect a backup. Isolate affected devices and report the incident first to avoid spreading the impact or damaging investigation evidence.
An attack may start with stolen accounts, phishing content or unpatched vulnerabilities. Not every incident begins with a staff member clicking by mistake.
A simplified path, not live monitoring or an inevitable sequence for every incidentAn HA active/standby pair mainly maintains service availability; it cannot replace ransomware prevention. Backups can help with recovery but cannot remove the risk of data already being leaked.
Learn about account protection and 2FAA staff computer is compromised. The attacker tries to use the stolen account to access shared files, servers and backups. Expanding access inside the network in this way is called “lateral movement”.
A firewall at the company's internet gateway does not mean access between internal devices is restricted. Shared administrator accounts may also increase the impact.
Assume this computer is already compromised. Isolation and permission restrictions can still help reduce further impact.
In this example, the stolen account can attempt to access servers and backups.
A simplified path, not live monitoring or an inevitable sequence for every incidentThe segmentation rules in this example deny the stolen account access to servers and backups. Actual effectiveness depends on permissions, rules and configuration; creating VLANs alone is not enough.
Practise verifying external support staffAsk the responsible person to check anything uncertain, then decide what improvements are needed.
“Implemented” should be backed by configuration or inspection records. This is a self-check, not a security certification. Selections remain on this page only.
Check the current position first, then arrange the next steps.
Compiled: 2026-10-08. These are original simulated scenarios, not client cases. Protection requires correct configuration, monitoring and incident response; it does not mean absolute security.
80 phishing scenarios and 8 everyday notices. Find the clues, then choose your next step. After answering, see the explanation within the email.
SPF, DKIM and DMARC check the relationship between sources and domains; they do not authorise payments, logins or data sharing for you.
Watch for the number 0, the letter O, lowercase l and uppercase I. Domains are case-insensitive; changing the case alone does not create a different domain.
GOOGLEG00GlEPractice URLs use the reserved .example/.invalid domains. Check the full hostname, not just a brand name or HTTPS.
The headers below were written for training; they are not live verification results. For real analysis, IT should check results added by a trusted receiving server; senders can forge header text.
Checks whether the sending server is authorised by the envelope sender domain; it does not directly verify the visible From identity. Forwarding may cause a failure.
Verifies the signing domain and the integrity of the signed parts. Pass does not mean the content is harmless or guarantee that the account has not been compromised.
At least one of SPF or DKIM must pass, and its domain must align with the visible From domain. A lookalike domain can also set up valid authentication for itself.
Keep the original email and send it to IT through your company reporting channel. Consider trusted headers, forwarding records and business context together; do not allow an attachment just because you see Pass.
Remove personal and company-sensitive information first. This tool only organises text; it does not detect malware or determine authenticity. It does not send data to a server, execute HTML, load images or open attachments.
Maximum 200 KB. MIME, HTML and attachments remain as raw text; they are not decoded or rendered.
One password, two protection settings. Follow the simulated login to see where the second factor makes a difference.
Original scenario illustration · Not a real attack recordVerify identity using two types of factor, such as a password and an authenticator. MFA is the general term for multi-factor authentication; entering two passwords is not 2FA.
The attacker has only your correct password and is trying to log in from an unfamiliar device. They do not have the second factor or an authenticated session. This example does not simulate other login restrictions.
Ready to compare: the same correct password, two different account settings.
Start the demonstration to see what could happen after a password leak.
This demonstration assumes a password plus a second factor is correctly enabled and enforced.
what would you do?
Choose a response to see why.
Ask the person responsible to confirm which accounts have enforced protection, which have exceptions and how to recover access safely after a lost phone. Make responsibilities for setup, checks and follow-up clear.
Ask about account security managementTick items only after checking them; refer anything unclear to the person responsible for follow-up.
Ticks are kept only on this page. This is not a system scan, compliance score or guarantee of account security.
Choose a topic and start the exercise. Submit your answer to see the safer action and its explanation.
0 answered · 0 correct
Answers are kept only on this page. Refreshing, reshuffling or changing topics resets this round’s results. No login or contact details required.
Preparing questions
Start the exercise, select an answer in the window, then confirm your choice.
Not answered yet
Original GDMME scenarios informed by public cybersecurity guidance. They do not test devices or rate business security.
Reference:CISA anti-phishing guidance. In-depth materials are available to authorised clients.
Learn how to arrange security awareness training for finance, administration and general staff.