[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-572979-105":53,"doc-detail-572979-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","device-security-requirements-version-10-revision-history","Device Security Requirements - Version 1.0 - Revision History","","Device Security Requirements defines security requirements for CPE devices across hardware and software components and their suppliers. It introduces a cyberattack lifecycle model focused on Intrusion, Exploitation, and Foothold Maintenance, aiming to make each phase too hard for attackers to achieve and keep threat risk manageable. The document specifies intrusion mitigations such as patch management, secure update and communication protocols, cryptographic capabilities, secure device management, administrative interface security, vulnerability management, and monitoring requirements, with additional sections for exploit and foothold mitigations.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/device-security-requirements-version-10-revision-history/572979/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/device-security-requirements-version-10-revision-history/572979.png","ImageObject",442,249,{"name":88,"@type":89},"lilac","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-18","2026-10-13",true,{"@type":98,"interactionType":99,"userInteractionCount":79},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of Device Security Requirements version 1.0?","Question",{"text":108,"@type":109},"It defines requirements to assure the security of CPE devices across hardware, software components, and their suppliers, using mitigations aligned to the attacker lifecycle model.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How does the document structure security mitigations?",{"text":113,"@type":109},"It groups mitigations by three attacker lifecycle parts: Intrusion, Exploitation, and Foothold Maintenance, with dedicated chapters for each mitigation area.",{"name":115,"@type":106,"acceptedAnswer":116},"What does patch management and update policy require?",{"text":117,"@type":109},"It requires launching devices with the most recent security patch versions, maintaining frequent updates, fixing known vulnerabilities before launch, and using secure and failsafe update mechanisms.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},572979,1792084905,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":79,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":15},3985747861865,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Device Security Requirements  \nVersion 1.0  \nREVISION HISTORY  \n\n| Version | Date | Authors | Description |\n| --- | --- | --- | --- |\n| 0.1 |  | Emilia Quijano (Verizon) | Initial Requirements from Verizon |\n| 0.2 |  | Brendan Black (Vodafone) | Merge Requirements from Vodafone |\n| 0.3 |  | Emilia Quijano (Verizon) | Merge Comments & Requirements |\n| 0.4 |  | Tomer Semo (SAM Seamless Network) | Restructure |\n| 0.5 |  | Tomer Semo (SAM Seamless Network) | Merge Comments from members such as Allot, Avast, Broadcom, BT, Deutsche Telekom, Intel, MaxLinear, McAfee, SAM Seamless Network, Verizon, and Vodafone. |\n| 1.0 | 16/11/2020 | Brendan Black (Vodafone), Dave Barr (MaxLinear) | Reformat for Initial Release (BB), Edited for clarity (DB) |\n\nCONTENT  \nCONTENT ...................................................................................................................3  \nABOUT THIS DOCUMENT...........................................................................................5  \n1. INTRODUCTION .................................................................................................5  \n2. INTRUSION MITIGATIONS .................................................................................7  \n2.1. PATCH MANAGEMENT AND UPDATE POLICY 7  \n2.2. CRYPTOGRAPHIC CAPABILITIES 8  \n2.3. SECURE FIRMWARE/SOFTWARE UPGRADE 10  \n2.4. SECURE DEVICE MANAGEMENT 11  \n2.5.ADMINISTRATIVE INTERFACES SECURITY 11  \n2.6.VULNERABILITY MANAGEMENT 16  \n2.7. MONITORING REQUIREMENTS 16  \n3. EXPLOIT MITIGATIONS ....................................................................................18  \n3.1. MEMORY CORRUPTION MITIGATIONS 18  \n3.2. RUNTIME INTEGRITY 18  \n3.3. SOFTWARE COMPONENTS 19  \n3.4. MICROSERVICES/CONTAINERS 19  \n3.5. MONITORING REQUIREMENTS 21  \n4. FOOTHOLD MAINTENANCE MITIGATIONS ......................................................22  \n4.1. SECURE BOOT 22  \n4.2. READ ONLY FILE SYSTEM 22  \n4.3. BINARY DECEPTION 23  \n4.4. MONITORING REQUIREMENTS 23  \n5. CONTACTS .......................................................................................................24  \n6. APPENDIX A: WIRELESS COMMUNICATIONS SPECIFICATIONS .......................25  \n6.1. WI-FI 25  \n6.2. Bluetooth Low Energy (BLE) Security 26  \n6.3. Z-Wave 27  \n6.4. ZigBee 27  \n6.5. Bluetooth Classic 27  \n7. APPENDIX B: LOGGING AND REPORTING SPECIFICATIONS ............................28  \n8. APPENDIX C: USER SERVICES ...........................................................................29  \n9. APPENDIX D: OMITTED BULLETS (AND REASONING) (INFORMATIVE) ..........30  \n10. REFERENCES AND FURTHER READING ............................................................33  \nABOUT THIS DOCUMENT  \n1. INTRODUCTION  \nThis document describes requirements to assure security of CPE Devices. The requirements span both hardware and software components, and their suppliers, such as SoC silicon vendors, BSPs, OEM system integrators, middleware providers, router operating systems, and high-level application developers.  \n● The categorization model that was used to raise and categorize the security requirements for a secured, future-proof firmware standard was the following:  \no From an attacker point of view, there are three main parts of a cyberattack lifecycle: Intrusion, Exploitation, and Foothold Maintenance.  \no Our goal is to make those three aspects too-hard-to-achieve by an attacker (meaning-to take the risk level of threats in each aspect to a manageable level), through dedicated mitigations via Firmware and Software.  \no Beyond mitigations, a crucial part of future-proofing the solution regarding all three aspects would be:  \n▪ Exposing an internal API for future security apps to be composed ontop of the stack.  \n▪ Provide a strong monitoring infrastructure, integrated at firmware level, which monitors attacker-created footprints and anomalies regarding the three aspects mentioned above. The data could be subscribed to by internal apps and solutions running on the firmwa","cbCaisQGjqLqyBTr","https://ap.wps.com/l/cbCaisQGjqLqyBTr","pdf",355380,33,"English","# ABOUT THIS DOCUMENT\n# 1. INTRODUCTION\n# 2. INTRUSION MITIGATIONS\n## 2.1. PATCH MANAGEMENT AND UPDATE POLICY\n## 2.2. CRYPTOGRAPHIC CAPABILITIES\n## 2.3. SECURE FIRMWARE/SOFTWARE UPGRADE\n## 2.4. SECURE DEVICE MANAGEMENT\n## 2.5.ADMINISTRATIVE INTERFACES SECURITY\n## 2.6.VULNERABILITY MANAGEMENT\n## 2.7. MONITORING REQUIREMENTS\n# 3. EXPLOIT MITIGATIONS\n## 3.1. MEMORY CORRUPTION MITIGATIONS\n## 3.2. RUNTIME INTEGRITY\n## 3.3. SOFTWARE COMPONENTS\n## 3.4. MICROSERVICES/CONTAINERS\n## 3.5. MONITORING REQUIREMENTS\n# 4. FOOTHOLD MAINTENANCE MITIGATIONS\n## 4.1. SECURE BOOT\n## 4.2. READ ONLY FILE SYSTEM\n## 4.3. BINARY DECEPTION\n## 4.4. MONITORING REQUIREMENTS\n# 6. APPENDIX A: WIRELESS COMMUNICATIONS SPECIFICATIONS\n## 6.1. WI-FI\n## 6.2. Bluetooth Low Energy (BLE) Security\n## 6.3. Z-Wave\n## 6.4. ZigBee\n## 6.5. Bluetooth Classic","[{\"question\":\"What is the purpose of Device Security Requirements version 1.0?\",\"answer\":\"It defines requirements to assure the security of CPE devices across hardware, software components, and their suppliers, using mitigations aligned to the attacker lifecycle model.\"},{\"question\":\"How does the document structure security mitigations?\",\"answer\":\"It groups mitigations by three attacker lifecycle parts: Intrusion, Exploitation, and Foothold Maintenance, with dedicated chapters for each mitigation area.\"},{\"question\":\"What does patch management and update policy require?\",\"answer\":\"It requires launching devices with the most recent security patch versions, maintaining frequent updates, fixing known vulnerabilities before launch, and using secure and failsafe update mechanisms.\"}]","Device Security Requirements - Version 1.0 - Revision History | PDF",1791930355]