# DBLinx Security: Login and Form Security | DBLinx > DBLinx Security protects login screens and forms against bot traffic: human verification on every login, and bot filtering with honeypot fields on forms. Source page: https://dblinx.net/en/smart360-security --- Security # DBLinx Security DBLinx Security is the security layer that protects login screens and forms across the DBLinx family against automated bot traffic. [See the products it protects](https://dblinx.net/en/ekosistem)[How does it work?](#nasil) - Human verification on web logins - Honeypot field on forms - Separate database per organization What it is ## What does DBLinx Security protect against? Protection doesn't get in the user's way: verification is usually completed in the background without any extra action. ### Password guessing attacks Automated password attempts on the sign-in screen do not reach the password check until human verification is complete. ### Fake form submissions Quote and contact forms are protected against automated submissions by human verification and a honeypot field. ### Form spam The invisible honeypot field in the contact form filters out submissions filled in by bots. Where it works ## Which screens does DBLinx Security cover? DBLinx Security is active at the user-facing entry points of the DBLinx family. A verification solved on another address is not considered valid on this page. Which screens does DBLinx Security cover? Screen | Protection | DBLinx organization dashboard sign-in | Human verification; the decision is made in the DBLinx Security service | DBLinx admin sign-in | Human verification; the decision is made in the DBLinx Security service | Quote form | Human verification and honeypot field | Contact form | Human verification and honeypot field | SmartMail and SmartFiles sign-in screens | The same human verification, with the same DBLinx Security look | How it works ## How is the verification decision made? For DBLinx dashboard sign-ins, the verification decision is made in a single central place: the DBLinx Security service. - The service returns the decision and, if needed, an explanation in Turkish to show to the user. - Secret verification keys are kept only in this central service; screens and products cannot access them. - The decision logic is built so that new check steps can be added without touching the screens. Screen DBLinx Security Decision Shared security across the family ## What other security layers does the DBLinx family have? DBLinx Security is the visible face of the family's shared security architecture. ### Separate database per organization Each organization's data is kept in its own separate database for each product; databases are never shared between organizations. ### Address-bound session SmartMail and SmartFiles sessions are bound to the organization address used to sign in; one organization's session is not valid on another organization's address. ### Single identity, central session management Active sessions are listed with device information and can be closed remotely; when the password changes, sessions on all devices are closed. [Details](https://dblinx.net/en/ekosistem) ### Encrypted mailbox passwords Mailbox passwords are generated by the system and stored encrypted with AES-256-GCM; they are not distributed to employees. [Details](https://dblinx.net/en/smartmail/paylasimli-kutu.html) ### Short-lived file links SmartFiles download and preview links expire within minutes; even if a link is forwarded, no permanent access is created. [Details](https://dblinx.net/en/smartfiles/onizleme.html) ### Five-layer attachment security Files attached to support tickets are checked on five layers: extension, content signature, size, storage key and download format. ### Central AI layer Products do not access AI services directly, but through DBLinx's central layer; usage is charged against the organization's entitlement. [Details](https://dblinx.net/en/yapay-zeka) ### Separate operations session The platform's operations dashboard is opened with a session separate from customer accounts, and its sign-in is protected by human verification. Email security ## How is corporate email protected? Email protection is SmartMail's own security layer. - Every incoming email is verified against SPF, DKIM, DMARC and PTR records. - Lookalike domains, brand impersonation and misleading links are each assessed separately, and the result is written with its reasoning. - Emails below the trust threshold are quarantined. - Emails sent on behalf of the organization can optionally go through approval. [SmartMail email security](https://dblinx.net/en/smartmail/guvenlik.html)[Email approval workflow](https://dblinx.net/en/smartmail/gonderim-denetimi.html)[SmartFiles field-based permissions](https://dblinx.net/en/smartfiles/yetkilendirme.html) SmartMail **SPF** **DKIM** **DMARC** **PTR** ## See the products it protects DBLinx Security verifies that web sign-ins are made by humans, filters out bot submissions on forms with honeypot fields, and explains its decision to the user in plain language. [SmartMail](https://dblinx.net/en/smartmail/)[SmartFiles](https://dblinx.net/en/smartfiles/)[SmartOperator](https://dblinx.net/en/smartoperator/)[SmartSales](https://dblinx.net/en/smartsales/)