DronaHQ

DronaHQ Security Best Practices

Building enterprise internal tools with DronaHQ? Make sure your database connectors and API integrations are properly secured.

Verify your app follows these best practices automatically.

These best practices are derived from the actual security findings we see in DronaHQ apps — not a generic OWASP list. Priority ordered: critical items close data-exposure gaps, high items prevent compromise, medium items reduce attack surface. Stack-specific guidance for Firebase included.

Quick Wins

Scan your deployed application with a security tool that understands this stack
Move all secrets server-side (environment variables, serverless functions)
Enable Row Level Security (Supabase) or Security Rules (Firebase) on every table
Enable audit logging for all data access and admin operations
Run a VAS scan against the deployed DronaHQ app

Security Best Practices

#1Over-Permissioned Database Connectors

medium

Connectors often use database accounts with full access. If compromised, the entire database is exposed.

Implementation

Scan your deployed application with a security tool that understands this stack. Address the specific findings — generic best practices don't catch platform-specific misconfigurations.

#2Shared API Credentials

high

API keys at the app level are shared across all users, making action tracing impossible.

Implementation

Move all secrets server-side (environment variables, serverless functions). Rotate any keys previously in frontend code. Audit bundles for leftover credentials before each deploy.

#3Server-Side Authorization Bypass

critical

Action flows may validate permissions in the UI but skip checks during server-side execution.

Implementation

Enable Row Level Security (Supabase) or Security Rules (Firebase) on every table. For custom backends, enforce authorization at the query layer — never client-side.

#4Close: Missing Audit Trail

medium

Enterprise compliance requires complete audit logs. DronaHQ apps may not log all data access events.

Implementation

Enable audit logging for all data access and admin operations. Retain logs per your compliance requirements (7 years for SOX, indefinite for some PCI scenarios).

Common Mistakes to Avoid

Over-Permissioned Database Connectors

Why it's dangerous:

Connectors often use database accounts with full access. If compromised, the entire database is exposed.

How to fix:

Scan your deployed application with a security tool that understands this stack. Address the specific findings — generic best practices don't catch platform-specific misconfigurations.

Shared API Credentials

Why it's dangerous:

API keys at the app level are shared across all users, making action tracing impossible.

How to fix:

Move all secrets server-side (environment variables, serverless functions). Rotate any keys previously in frontend code. Audit bundles for leftover credentials before each deploy.

Server-Side Authorization Bypass

Why it's dangerous:

Action flows may validate permissions in the UI but skip checks during server-side execution.

How to fix:

Enable Row Level Security (Supabase) or Security Rules (Firebase) on every table. For custom backends, enforce authorization at the query layer — never client-side.

Missing Audit Trail

Why it's dangerous:

Enterprise compliance requires complete audit logs. DronaHQ apps may not log all data access events.

How to fix:

Enable audit logging for all data access and admin operations. Retain logs per your compliance requirements (7 years for SOX, indefinite for some PCI scenarios).

Verify Your DronaHQ App Security

Following best practices is the first step. Verify your app is actually secure with a comprehensive security scan.

Get Starter Scan

Frequently Asked Questions

What's the minimum security I need for a DronaHQ app?

The critical-priority items above are non-negotiable for any DronaHQ app that handles user data: server-side authorization bypass. Everything else is iterative.

Should I run a security scan before launching a DronaHQ app?

Yes — unconditionally. The mitigations above are specific enough that a scan proves they're implemented correctly. "I followed the checklist" isn't evidence; "the scan came back clean" is.

Is DronaHQ secure by default?

DronaHQ provides secure infrastructure, but the application-layer configuration (listed above) is the developer's job. The default state of a DronaHQ app before any security work typically has at least one critical-priority issue open.

Last updated: April 2026