Table 3 IoT Vulnerabilities and Proposed Solution Benefits.
From: Resilient security architecture for smart buildings using DLT powered encryption
Category | Vulnerabilities | Impact | Proposed Solution | Security Benefits |
|---|---|---|---|---|
Authentication & Access Control50 | \(\bullet\) Device spoofing \(\bullet\) Weak authentication \(\bullet\) Unauthorized access | \(\bullet\) Network compromise \(\bullet\) Data theft \(\bullet\) Device hijacking | \(\bullet\) Cryptographic device signatures \(\bullet\) DLT-based identity verification \(\bullet\) Secure authentication protocols | \(\bullet\) Strong device identity verification \(\bullet\) Tamper-evident access logs \(\bullet\) Reduced unauthorized access risk |
Data Integrity51 | \(\bullet\) Data manipulation \(\bullet\) Tampering during transit \(\bullet\) False data injection | \(\bullet\) Incorrect sensor readings \(\bullet\) System malfunction \(\bullet\) Decision-making errors | \(\bullet\) Immutable ledger records \(\bullet\) Cryptographic validation \(\bullet\) Distributed consensus | \(\bullet\) Guaranteed data authenticity \(\bullet\) Traceable data lineage \(\bullet\) Tamper-resistant storage |
Network Security52 | \(\bullet\) Man-in-the-Middle attacks \(\bullet\) DDoS attacks \(\bullet\) Traffic analysis | \(\bullet\) Service disruption \(\bullet\) Data interception \(\bullet\) Network congestion | \(\bullet\) End-to-end encryption \(\bullet\) Distributed architecture \(\bullet\) Reduced network overhead | \(\bullet\) Enhanced traffic resilience \(\bullet\) Improved network stability \(\bullet\) Reduced attack surface |
Resource Management53 | \(\bullet\) Memory constraints \(\bullet\) Processing limitations \(\bullet\) Battery drainage | \(\bullet\) Limited security features \(\bullet\) Performance degradation \(\bullet\) Device failure | \(\bullet\) Optimized resource utilization \(\bullet\) Efficient encryption \(\bullet\) Balanced workload distribution | \(\bullet\) Sustainable security measures \(\bullet\) Extended device lifetime \(\bullet\) Consistent performance |
Scalability54 | \(\bullet\) Network congestion \(\bullet\) High latency \(\bullet\) Transaction bottlenecks | \(\bullet\) System slowdown \(\bullet\) Increased costs \(\bullet\) Reduced reliability | \(\bullet\) IOTA’s scalable architecture \(\bullet\) Low-cost transactions \(\bullet\) Improved throughput | \(\bullet\) Enhanced system responsiveness \(\bullet\) Cost-effective operation \(\bullet\) Better performance at scale |
Privacy55 | \(\bullet\) Data leakage \(\bullet\) Unauthorized monitoring \(\bullet\) Sensitive information exposure | \(\bullet\) Privacy breaches \(\bullet\) Regulatory non-compliance \(\bullet\) Trust issues | \(\bullet\) Confidential transactions \(\bullet\) Access control mechanisms \(\bullet\) Encrypted data storage | \(\bullet\) Protected sensitive data \(\bullet\) Regulatory compliance \(\bullet\) Enhanced user trust |
Smart Contract Security56 | \(\bullet\) Contract vulnerabilities \(\bullet\) Logic errors \(\bullet\) Execution flaws | \(\bullet\) Financial losses \(\bullet\) System exploitation \(\bullet\) Security bypass | \(\bullet\) Automated security policies \(\bullet\) Verified contract execution \(\bullet\) Secure deployment protocols | \(\bullet\) Reduced human error \(\bullet\) Consistent policy enforcement \(\bullet\) Automated security responses |
Real-time Monitoring57 | \(\bullet\) Delayed detection \(\bullet\) Missed incidents \(\bullet\) Incomplete logging | \(\bullet\) Security gaps \(\bullet\) Slow incident response \(\bullet\) Limited forensics | \(\bullet\) Continuous validation \(\bullet\) Real-time anomaly detection \(\bullet\) Comprehensive logging | \(\bullet\) Quick incident detection \(\bullet\) Improved response time \(\bullet\) Better forensic capabilities |