Netblinks is designed to help authorized business users explore operational data while preserving database, identity and workspace controls. This overview describes current design principles and is not a certification, warranty or service-level agreement.
1. Identity and Authentication
The Netblinks SaaS application uses centralized identity through Keycloak. Protected middleware endpoints validate signed access tokens, including issuer and audience checks. Customers remain responsible for managing their authorized users and promptly removing access that is no longer required.
2. Authorization and Tenant Separation
Application data is associated with a tenant or workspace. Middleware authorization checks use the authenticated user’s membership and role. Administrative operations are restricted to the appropriate owner or administrator roles, and unlisted gateway operations are denied by default.
Logical tenant separation reduces the risk of one customer accessing another customer’s application data. It does not replace careful operational configuration, monitoring and testing.
3. Database Access and Query Protection
Netblinks supports MySQL, PostgreSQL and Microsoft SQL Server connections. Customers control which databases are connected and which permissions are granted.
Customers should use dedicated, least-privilege credentials and read-only database permissions wherever appropriate. Netblinks applies authorization and query controls, but no application safeguard should be treated as a substitute for database-level permissions, backups and monitoring.
4. Credential Protection
Database credentials and customer-provided AI-provider keys are treated as secrets. The application is designed to send secrets to the protected Core service for encryption and retain encrypted ciphertext rather than plaintext in the middleware database.
Credential access should be restricted to the minimum services and personnel needed to operate the requested integration. Secrets should not be entered into support messages or public forms.
5. AI Provider Controls
Netblinks supports Netblinks-managed AI and customer-directed bring-your-own-key configurations. The active model and provider are workspace-controlled, subject to subscription authorization. Customer-provided keys remain subject to the customer’s agreement with the selected provider.
AI output may be inaccurate or incomplete. Users should review generated queries, supporting data and interpretations before consequential use.
6. Application and Service Controls
Current design controls include:
- signed-token authentication;
- workspace membership and role checks;
- tenant-scoped repositories and records;
- explicit gateway route authorization;
- subscription and entitlement enforcement;
- controlled internal administrative endpoints;
- request identifiers and operational logging; and
- encrypted handling of customer-supplied AI credentials.
8. Reporting a Security Concern
Please report suspected vulnerabilities or security incidents privately to support@netblinks.com. Do not include passwords, API keys, database credentials or production data in the initial message.
Netblinks will use commercially reasonable efforts to review legitimate reports. Do not test against customer or production systems without prior written authorization.