Establish a clear network boundary
Review internet lines, wired devices and the connections your business needs.
Plan equipment around
your business connections
Explore firewall configurations, rental plans and active–standby planning. Models, licences and delivery arrangements are confirmed in your proposal.
GDMME / EQUIPMENT PLANNINGStart with your workplace
Start with your workplace
Choose a suitable equipment plan
You do not need a model number to start. Share your team size, locations and critical connections so we can discuss equipment, licences and management.
Plan access between your workplaces
Outline branch connections, remote access and who should reach each system.
Assess active–standby deployment
Identify services that need continuity, then confirm compatibility and failover testing.
The agreed configuration and quotation identify the equipment model, available functions and support scope.
GDMME HARDWARE / Business security equipment
The value of equipment
Realised through professional management
GDMME Appliance is the brand's equipment range. Its current focus is business cybersecurity, with MSS professional managed services connecting equipment to day-to-day management.
01Confirm the purposeConfigure for network and operational needs
02Provide ongoing careAssign responsibility for configuration, updates and maintenance
03Arrange supportRecord fault handling and responsibilities
THE EQUIPMENT GALLERY / Equipment gallery
R&D concept · Specifications subject to engineering validationFrom the exterior to configuration details
1+1
Dual power suppliesReduce power supply risk
The design aims to use two redundant power supply modules, each capable of supporting the full design load independently. A/B power paths are planned according to site conditions.
Items for engineering validation
Power supply dimensions, power headroom, redundant backplane, hot-swap support, cooling and fault alerts must all be validated with the actual motherboard and modules.
ACTIVE / STANDBYActive/standby pair
The active unit keeps running
The standby unit stays ready
Two compatible appliances form an HA pair. One handles day-to-day connections while the other remains on standby. When fault criteria are met, the standby unit takes over supported services according to the configuration.
- Active unit roleACTIVE
- Handle daily traffic and security policy processing, and synchronise settings or connection states where supported.
- Standby unit roleSTANDBY
- Continuously check the active unit's status and stay ready to take over when needed. After takeover, it becomes the active unit providing service.
A/B illustrate the roles during normal operation. Active and standby roles may change after takeover.
After takeover
Confirm service, then address the fault.Administrators must still check connections, repair faulty equipment and arrange a return to standby or failback under established rules.
How do dual power supplies, active/standby HA and backups differ?
- Dual power supplies
- Provide power redundancy within one appliance. Failure of the entire appliance still requires separate arrangements.
- Active/standby HA
- Another appliance takes over services to reduce the risk of a single appliance failure. Actual downtime and connection retention must be tested.
- Data backups
- Retain copies of data for recovery. HA synchronisation cannot replace backups.
This describes active/standby mode, not two appliances sharing traffic simultaneously. Available features must be confirmed for the equipment, network and proposal.
One unit handles operations
The other is ready to take over
HA pairs two compatible appliances in active/standby roles. The active unit handles connections; the standby unit checks status and synchronises settings or connection information according to the configuration.
Automatically looping illustrationNot live equipment status
Active unit A handles connections. Standby unit B continuously checks status and synchronises data where supported.
Dual power supplies protect power delivery; HA reduces the risk of a single appliance failure.They work together. HA also cannot replace data backups.
What should be confirmed before deployment?
Confirm the synchronisation scope, fault criteria, shared switch and connection risks, VPN/module compatibility and recovery procedures after failover. Actual downtime must be tested. The animation does not represent failover speed or guarantee zero downtime.
Further reading: Netgate HA architecture
For understanding general principles. This is not certification of GDMME models or features.
Four considerations before configuration
- Network scaleUser numbers, locations, connections and actual traffic needs.
- Enabled featuresRequired security checks, remote access and management tasks.
- Deployment environmentRack space, power, cooling and compatibility with existing systems.
- Maintenance arrangementsUpdate windows, redundancy requirements and fault handling.
Models, hardware specifications and available features are confirmed for each service proposal.
EQUIPMENT, WITH RESPONSIBILITYGood equipment
Good equipment
Also needs good management
From computers and accounts to important data, identify the work that needs ongoing attention, then arrange managed services that suit your business.
Start with what matters to youPublic interactive scam awareness classroom
PEOPLE BEHIND THE PROTECTIONA business office scenario in Central
Someone is responsible for every follow-up.Checks, records and follow-up, arranged around your business needs.
Original service scenario illustration
DEFENCE, EXPLAINED / How protection works together
Clear separation for clear management
Separate office, guest and critical systems, with access set according to purpose.
Interactive architecture illustration
THE ARCHITECTURE OF TRUST
Trust
Built from the ground up
Processing power, data and intelligence each have a clear role.
Bring every layer of protection into an architecture you can understand and manage.
Appliance processing power
Matched to actual workloads
Use business-grade equipment for layered protection, planning the configuration around connection scale, enabled features and maintenance needs.
Processor platforms, packet acceleration methods and performance are confirmed according to the equipment model and test conditions.
Data boundaries
Defined by you
From log retention and access permissions to retention periods, build data-handling responsibilities into the deployment plan.
The scope of local retention and external intelligence exchange is clearly defined in the data flows and service proposal.
Global intelligence
Applied to local decisions
Combine external threat intelligence with your business environment so that blocks, exceptions and alerts have a traceable basis.
Integration, licensing and configuration of Zenarmor, CrowdSec, Geo-IP and AI modules are confirmed for each proposal.
The IP country / region is shown according to the IP database; the place of registration is unverified and does not indicate the actual location.
The IP country / region is shown according to the IP database; the place of registration is unverified and does not indicate the actual location.
The visuals illustrate architectural concepts. Available features and deliverables are subject to the confirmed service proposal.
GDMME / STRUCTURE & DESIGN
See the thinking inside the structure
Explore the design intent behind the intake grille, light strip and the space within the chassis
Structure and airflow concept · Actual configuration requires engineering confirmation
View the complete drawingFront intake grille
Give airflow a clear starting point
Separate the front intake area from the cable connections to make the layout easier to read and inspect. The opening ratio, dust protection and intake performance require component selection and thermal testing.
Soft light strip
Integrate identity into the panel
A restrained light strip gives the panel a GDMME identity and offers a possible status-display interface. Brightness, colours and signal meanings depend on the model; the illustrated light does not show a running device.
Grouped network ports
Make connections easier to identify
Group interfaces with clear space for labelling, cabling and maintenance. Port counts, speeds and module combinations are confirmed against the selected model and the business network requirements.
Removable cover
Plan for maintenance access
The exploded view shows how the cover relates to the chassis, helping discuss inspection and service access. Fastenings, opening procedures and authorised access must follow the actual device’s maintenance requirements.
Rack mounting points
Confirm support before installation
The front rack ears illustrate positioning and attachment. Hole spacing, rack compatibility and any need for rails or a shelf must be confirmed for the equipment weight and installation environment.
Internal layout and airflow
Coordinate layout with cooling
Internal zones and a proposed front-to-rear airflow path help discuss components, cabling and cooling together. Internal parts are illustrative envelopes, not an actual PCB; airflow direction and cooling performance require engineering review and thermal testing.
This image explains design intent and is not a to-scale CAD manufacturing drawing
Discuss an equipment configurationGDMME / MANAGEMENT INTERFACE PREVIEW
Your network. Under control.
From deployment to daily management, give administrators a clear entry point and agree configuration and access by authorisation.
Interface previewView the management interface preview
Display only · No account details required
FIREWALLNETWORK SECURITY. YOUR WAY.
NETWORK · POLICY · ACCESS
Your network.Under control.
See your network clearly, shape its policies and control access by authorisation.
NETWORK · POLICY · ACCESSAPPLIANCE ACCESS
Sign in
Use your assigned account to continue.
Account assistance: Contact your administrator.This illustrates the sign-in design without connecting to a device or collecting sign-in details. The actual interface and features depend on the device version and deployment.
Discuss equipment and management →CROWDSEC / DEFENCE INTEGRATION
CrowdSec integration & ongoing improvements
Integration & ongoing improvements
GDMME plans to integrate CrowdSec in stages and review and improve configurations over time, connecting attack behaviour in service logs with collaborative threat intelligence and enforcement in equipment and managed security proposals. Available functions and scope depend on each deployment’s configuration and validation results.
Planned defence workflow
- 01Read configured logs
- 02Evaluate behaviour scenarios
- 03Generate decisions
- 04Compatible components enforce
Behaviour detection
Analyse configured service logs against detection scenarios to identify attack behaviour and generate alerts and decisions.
Collaborative threat intelligence
Use CrowdSec threat intelligence according to deployment settings. Community signal sharing and the data involved will be agreed in the proposal.
Enforcement and ongoing management
Enforce decisions through compatible remediation components, with alert review, rule updates, allowlists and unblocking included where agreed in the managed scope.
What is agreed before deployment?
Agree log sources and retention, compatible components, blocking and unblocking, false-positive handling, coverage hours and responsibilities. The proposal also explains threat intelligence and community signal sharing settings.
Agree log sources, compatible components, decision duration and follow-up responsibilities before deploying and validating detection through to enforcement.
WAF / AppSec can be assessed separately and requires compatible components and rules. Included functions will be specified in the proposal.
HUORONG / BUSINESS ENDPOINT SECURITY
Huorong Enterprise: bring endpoint management together
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.
Huorong Endpoint Security Management System 2.0
Central management and policy distribution
Group endpoints by department or role, review status, assets and security logs, and distribute protection policies. Confirm that endpoints are connected and policies have synchronised.
Microsegmentation: restrict lateral connections
Use endpoint IP protocol controls to restrict inbound and outbound connections, alongside application network rules, so departments reach only required services. This policy-based endpoint segmentation needs business connectivity testing.
Second-factor protection for administration and key endpoints
Enable dynamic authentication for the control centre. Supported endpoints can also require a dynamic code for local password sign-in and Remote Desktop sign-in. Scope this for compatible key servers; configure firewall and switch administration MFA separately where supported.
Review detected vulnerabilities and installed applications
Review connected endpoints’ vulnerabilities, installed software and remediation status centrally, scheduling tested updates within maintenance windows. Coverage follows the supported catalogue and does not constitute a complete vulnerability scan of every application.
USB storage and USB Wi-Fi controls
Apply policies to USB storage, USB wireless / wired adapters and other peripherals, with blocking and trusted-device exceptions. Supported storage can be read-only, reducing unauthorised connections and file introduction risks.
Restrict unauthorised remote tools
Restrict specified remote tools through execution controls and network rules. Software prohibition can separately log, prompt or isolate non-compliant endpoints according to policy. Validate application matching and retain an approved maintenance channel.
Internal connections need boundaries too
Segmentation example: finance PCs can use an approved application; general staff PCs cannot directly access finance PCs or core equipment administration ports.
Staff PC
×
Cross-department access restricted
Finance PC
✓
Retain required business access
Approved business app
Huorong control centre → group policies → endpoint enforcement and logs
Illustrative rules, not live monitoring. Enable and synchronise policies on managed endpoints. Agentless devices, uncovered paths and core equipment also need network segmentation, access controls and other protection.
Dynamic authentication has version and account restrictions: local sign-in methods may change, and some high-risk operation checks exempt super administrators. Agree recovery and emergency access before deployment.
Functions vary by operating system, edition, licence and endpoint type. GDMME reviews compatibility and tests policies before agreeing deployment, service hours and deliverables.
CHOOSING YOUR DEFENCE / PROPOSAL COMPARISON
How does GDMME + CrowdSec compare with major-brand solutions?
CrowdSec integration & ongoing improvements
GDMME aims to connect equipment, collaborative threat intelligence and local management in a clear service arrangement. Compare actual protection scope, licensing and follow-up ownership.
This explains GDMME’s proposed approach and questions to check in major-brand quotations. Vendors offer different deployment and managed options; compare the specific products, editions and service agreements.
| Dimension | GDMME + CrowdSec (planned approach) | Major-brand proposal (items to confirm) |
|---|---|---|
| Starting point | Scope around Hong Kong businesses’ equipment, working environment and management needs, documenting configuration and follow-up ownership. | Does the selected edition fit staff, sites and existing equipment? Who provides deployment and ongoing management? |
| Threat intelligence and detection | Plan behaviour detection from configured logs with CrowdSec, alongside community blocklists and selected intelligence subscriptions. | Which intelligence, detection engines and updates are included? Which require subscriptions? Can third-party intelligence be imported? |
| Deployment and enforcement | Select compatible remediation components and validate alerts, enforcement, allowlists and unblocking. | Which appliance, virtual, cloud or agent deployments are supported? How are throughput and feature limits defined? |
| Endpoint and network responsibilities | Plan layers across GDMME network equipment, CrowdSec integration and Huorong Enterprise; confirm endpoint licensing and functions separately. | What is included for firewall, EPP, EDR and WAF? Are integrations and licences included? |
| Management and support ownership | Document alert review, updates, handover records, service hours and escalation contacts in the GDMME engagement. | Is support owned by the vendor, distributor or managed team? Are coverage hours, response commitments and incident support agreed in writing? |
| Licensing and total cost | Itemise equipment, deployment, endpoint licences, selected CrowdSec intelligence / Console plans and management. An open-source engine does not make all data or commercial use free. | Compare licences, renewals, replacement, deployment and management for equivalent scope, including the impact of expiry or disabled features. |
Existing major-brand equipment can be assessed for compatible integration and management. GDMME proposes a scope around your current environment.
SECURITY PRODUCTS
Security technology with local service
WebRAY (盛邦安全) security products are provided by distributor AL-TOUCH SOLUTIONS LIMITED 一大方案有限公司. Businesses can discuss vulnerability assessment and application security requirements, with equipment, licensing and deliverables specified in each proposal.
WebRAY (盛邦安全) provides vulnerability management, Web application protection, API security and network security products. GDMME discusses product selection, deployment and management around business requirements, identifying selected products and licences in the proposal.
How the proposal supports your business
Product selection and licensing
Review asset scope, compatibility and assessment objectives, and identify selected products, editions, modules and licences.
Deployment and configuration
Plan deployment around agreed access and timing, recording configuration, test results and coordinated changes.
Management and follow-up
Agree findings review, updates, remediation follow-up and retesting within the engagement, keeping outstanding actions visible.
Start with your business as it is todayGive security work
Discuss your security needsGive security work
clear ownership
Tell us your company size and main needs, and we can define a suitable scope together.