01 / IDENTITY
Authentication
Verify user or device identity before protected access is granted.
HeliControl / Cybersecurity
See the threat. Trace the signal.
Security events, detection and alert monitoring for the HeliControl simulator environment.
SECURITY MONITORING CONCEPT
HELICONTROL
THREAT MONITOR
EVENT / AUTH
LOGIN_FAILED
EVENT LOG
API SECURITY
IOT_AUTH_FAILURE
REJECT / LOG
ACCESS CONTROL
ACCESS_DENIED
SECURITY EVENT
EVENT LOG
REPEATED_LOGIN_FAILURE
ALERT EXAMPLE
DIGITAL WATERFALL / HUD
SECURITY MONITORING CONCEPT
01 / Security Pipeline
Layer by layer.
Control the attack surface.
Security controls are applied at the relevant backend stage. The exact processing depends on the event and the implemented rule.
HELICONTROL SECURITY CONTROL CHAIN
REQUEST → REVIEW
02 / PERMISSION
Authorisation
Enforce role permissions at the backend, not just in the interface.
03 / API
Request Validation
Validate the request, credentials and required input fields.
04 / TRACE
Security Logging
Record relevant events so activity can be reviewed.
05 / DETECTION
Detection Rules
Evaluate supported patterns or repeated events when applicable.
06 / ALERT
Alert Handling
Create a security alert when the applicable rule calls for it.
07 / REVIEW
Admin Monitoring
Review eligible security alerts and their status.
08 / DELIVERY
Notification Flow
Push delivery depends on the implemented backend and FCM flow.
Architecture boundary: Flutter and the Door/Telemetry ESP8266
devices communicate through PHP backend APIs. They do not connect directly to MySQL.
02 / Event → Alert
An event is not always
an actionable alert.
Event logs record activity. Security alerts flag conditions that require review. Those two things should not be treated as identical.
Security Event Log
Record what happened
LOGIN_FAILED
Failed authentication event
AUTH_FAILURE
Authentication-related event
ACCESS_DENIED
Access request denied
INVALID_API_KEY
Credential rejection example
One
LOGIN_FAILED event does not automatically become a
REPEATED_LOGIN_FAILURE alert.
Security Alert
Surface a condition for review
01
REPEATED_LOGIN_FAILURE
Documented rule: at least five failed attempts from the same IP within five minutes.
02
IOT_AUTH_FAILURE
Example: an IoT request is missing a valid API key or authentication credential.
03
IOT_ACCESS_DENIED
Example: an IoT access request is rejected by the relevant access rules.
Alert creation, cooldown, deduplication, notification delivery and
resolution are governed by the real implementation. The panel below
demonstrates the concepts locally.
03 / Security Monitor
Trigger a scenario.
Inspect the response.
Select a scenario and see its local event log, security alert, lifecycle status and notification preview.
LOCAL SIMULATION ONLY.
This browser demo does not send login attempts, call IoT APIs,
write to MySQL or send actual FCM push notifications.
SECURITY MONITOR / DEMO
0 LOCAL EVENTS
EVENT LOGS
0
Local demo records
ACTIVE ALERTS
0
Security alerts
RESOLVED
0
Local status only
RECENT SECURITY EVENTS
WAITING FOR EVENT
Choose a scenario to start the demonstration.
TEST SCENARIOS
DEMONSTRATION STATUS
READY
Choose a scenario and press APPLY SCENARIO.
SECURITY ALERTS
No security alert has been created in this demo.
NOTIFICATION PREVIEW
FCM NOT SENT
Local notification previews will appear here.
These are visual examples only; they do not prove real FCM delivery
or database persistence.
04 / Security Principles
Defence starts
before detection.
The PHP backend/API is the security boundary. The mobile UI and devices must rely on server-side authentication and permissions.
LAYER 01 / IDENTITY
Authentication
Verify user or device credentials through the relevant backend endpoint.
LAYER 02 / PERMISSIONS
Role-Based Authorisation
Enforce Pilot/Admin permissions in the backend; hiding a button alone is insufficient.
LAYER 03 / INPUT
API Validation
Validate incoming requests and reject invalid or unauthorised requests appropriately.
LAYER 04 / VISIBILITY
Security Logging
Record relevant authentication and access activity for further review.
LAYER 05 / DETECTION
Alert Rules
Distinguish event logs from alerts that meet a specific detection condition.
LAYER 06 / LIFECYCLE
Alert Management
Allow resolution only for eligible security alerts; keep operational and security flows separate.
Continue Exploring
Security is a workflow, not just a screen.
Explore the mobile interface, IoT architecture and simulator demonstration to understand how each HeliControl component fits together.