| 1 | Data Encryption at Rest | Use authenticated encryption such as AES-128-GCM or AES-256-GCM for stored credentials, tokens, and configuration data. AES-256 is preferred where performance and hardware support allow it. | Encryption architecture, algorithm and mode specification, key-storage design, and an independent security test report. | “AES encrypted” is stated without identifying the mode, key protection, or protected data. | 15% |
| 2 | Communication Encryption | Protect mobile-app, gateway, and cloud communications with TLS 1.2 or higher, strong certificate validation, and secure random session keys. | Protocol configuration, certificate-validation behavior, penetration-test results, and network data-flow documentation. | Unencrypted local API traffic, disabled certificate checks, or reliance on proprietary encryption without technical documentation. | 12% |
| 3 | Secure OTA Updates | Firmware updates should be digitally signed, verified on the lock, transmitted securely, and protected against downgrade attacks. A recovery or rollback mechanism is recommended. | Update workflow, signing-key control process, signature-verification test, rollback plan, and published support period. | Unsigned firmware, manual update files from unknown sources, no rollback process, or no stated end-of-support date. | 15% |
| 4 | Secure Boot and Hardware Protection | Use a verified boot chain, protected bootloader, debug-port control, and secure storage for device keys where supported by the hardware platform. | Hardware security architecture, production configuration, debug-lock evidence, and laboratory attack-test results. | Open debug interfaces, shared device keys, undocumented bootloader access, or identical credentials across units. | 12% |
| 5 | Audit Logs and Event Integrity | Record unlocks, failed attempts, credential changes, administrator actions, firmware updates, and configuration changes with synchronized timestamps. | Sample log export, event-field list, retention policy, access-control policy, and evidence that logs cannot be silently modified. | Logs omit failed attempts or administrator actions, lack timestamps, are easily deleted, or cannot be exported. | 12% |
| 6 | Authentication and Access Control | Support unique administrator accounts, least-privilege roles, strong password rules, session timeout, credential revocation, and optional multi-factor authentication for management portals. | Role-permission matrix, account-management screens, password policy, revocation test, and administrator audit records. | Shared administrator accounts, permanent installation passwords, unlimited login attempts, or no way to revoke lost credentials. | 12% |
| 7 | Randomness and Credential Protection | Generate keys, reset tokens, and temporary access codes with a cryptographically secure random number generator. Store passwords using salted, adaptive hashing rather than reversible encryption. | Credential-storage design, random-number-generation details, code-expiration rules, and security-assessment findings. | Predictable PINs, reusable temporary codes, plaintext credentials, or one universal master code. | 10% |
| 8 | Vulnerability Management | Maintain a vulnerability-reporting channel, risk-based remediation targets, dependency monitoring, and a documented process for security advisories. | Incident-response procedure, vulnerability disclosure policy, patch records, responsible contact, and sample remediation timeline. | No security contact, no patch history, unclear ownership after shipment, or refusal to discuss vulnerability handling. | 8% |
| 9 | Privacy and Data Governance | Define what personal data is collected, where it is stored, who can access it, how long it is retained, and how data deletion or export requests are handled. | Data-flow diagram, privacy policy, retention schedule, deletion procedure, subprocessors list, and applicable compliance documentation. | Undisclosed cloud storage, indefinite retention, unnecessary collection of biometric data, or no account-deletion process. | 7% |
| 10 | Independent Testing and Security Documentation | Require current penetration testing, threat modeling, secure-development procedures, and applicable product safety or cybersecurity conformity evidence. | Test scope and date, unresolved-findings summary, threat model, secure-development lifecycle documents, and relevant certification or conformity records. | Generic certificates unrelated to cybersecurity, outdated reports, incomplete test scope, or refusal to provide evidence under confidentiality terms. | 7% |