schema · 17 fields
cybersécurity for iot devices
Automate extraction for "cybersécurity for iot devices ". Extract structured, evidence-grounded data points directly from hundreds of papers with source page coordinates.
Schema Field Definitions (17)
| Field Name | Data Type | Description |
|---|---|---|
| study_title | string | The title of the scientific paper or study. |
| year_published | number | The year the source paper was published, as an integer. Example: 2024. |
| device_manufacturer | string | The manufacturer of the studied IoT device. Example: 'Cisco' or 'Xiaomi'. |
| device_model | string | The specific model identifier of the IoT device. Example: 'SmartCam SNH-V6410PN'. |
| device_type | string | The category of the IoT device being analyzed. Must be one of: Smart Home Appliance, Industrial Sensor, Medical Device, Wearable, Network Router, Camera/Surveillance, Automotive System, Drone. |
| operating_system | string | The operating system running on the device. Must be one of: Linux, Android Things, RTOS, Windows IoT, Proprietary. |
| vulnerability_identifier | string | The standard identifier for the vulnerability, such as a CVE ID. Use 'N/A' if no official ID is available. Example: 'CVE-2023-12345'. |
| vulnerability_type | string | The category of the vulnerability reported. Must be one of: Buffer Overflow, SQL Injection, Denial of Service (DoS), Cross-Site Scripting (XSS), Authentication Bypass, Weak Credential Management, Firmware Tampering, Man-in-the-Middle (MITM). |
| cve_severity_score | number | The Common Vulnerability Scoring System (CVSS) base score (v3.1) as a floating-point number. Use 0.0 if not applicable. |
| cve_severity_score_unit | string | The unit for the CVSS score. Must be 'CVSS Score (v3.1)'. |
| attack_vector | string | The method used to initiate the attack. Must be one of: Network, Adjacent Network, Physical, Local, Remote, Supply Chain. |
| mitigation_mechanism | string | The type of security defense or mitigation employed in the study. Must be one of: Encryption, Authentication Protocol, Intrusion Detection System (IDS), Firmware Update, Access Control, Hardware Security Module (HSM), Isolation/Sandboxing. |
| protocol_tested | string | The communication protocol analyzed or secured. Must be one of: MQTT, CoAP, Zigbee, Bluetooth Low Energy (BLE), HTTP, TLS/SSL, Thread, Wi-Fi. |
| security_overhead_percentage | number | The computational or bandwidth overhead introduced by the security mechanism, expressed as a floating-point percentage. |
| security_overhead_percentage_unit | string | The unit for security overhead. Must be '%'. |
| is_successful_mitigation | boolean | Indicates if the proposed mechanism successfully mitigated the reported vulnerability. Must be true or false. |
| doi | string | The Digital Object Identifier (DOI) or a full bibliographic reference for the source paper. |
Data Verification Status Taxonomy
To maintain rigorous scientific standards, Sci-database differentiates between automated signals and human audit:
Extracted
Value located and extracted from the full-text PDF by the Kateeb engine.
Model-Agreed
An independent second model produced a compatible value during automated second-pass review.
Human-Reviewed
A named researcher audited the value against the visual page coordinates.
Benchmark-Validated
Performance evaluated against a standardized, published evaluation protocol.
Replicated
An independent external research group reproduced the extraction and experimental result.