[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"framework:iso-27001\u002Fa-5-30":3},{"item":4,"lessons":16,"controls":22,"related":27},{"family":5,"item":6,"code":7,"title":8,"citations":9,"publisher":10,"summary_md":11,"official_text":12,"official_attribution":12,"official_url":13,"link_label":14,"note":12,"updated_at":15},"iso-27001","a-5-30","Annex A 5.30","ICT readiness for business continuity",1,"International Organization for Standardization (ISO) and IEC","**What it asks for.** ICT readiness should be planned, implemented, maintained and tested based on business continuity objectives and ICT continuity requirements, so that technology can be recovered in time to support critical activities.\n\n**In practice.** Recovery time and recovery point objectives come from a business impact analysis and are mapped to the systems and dependencies that support each critical process. Technical recovery plans exist for those systems, and recovery is exercised regularly, including full restores from backup rather than just backup job success. Results are compared with the objectives and gaps are fixed. Evidence includes the impact analysis, recovery plans, test reports and records of follow up actions.\n\n**Common gaps.** Objectives are often set by the business but never validated against what IT can actually deliver. Tests tend to cover individual servers rather than end to end services, and cloud and SaaS dependencies are frequently assumed to be resilient without evidence.",null,"https:\u002F\u002Fwww.iso.org\u002Fstandard\u002F27001","See the standard at ISO","2026-10-18T15:18:43.664+00:00",{"total":9,"list":17},[18],{"slug":19,"title":20,"published_at":21},"ai-powered-near-autonomous-attack-targets-apac-government-agencies","AI-Powered Near-Autonomous Attack Targets APAC Government Agencies","2026-08-19T02:20:28.128+00:00",[23],{"slug":24,"name":25,"problem":26,"stories":9},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them.",[28,33,37,41,45,49,54,58],{"family":29,"item":30,"code":31,"title":32,"together":9},"cis","13","Control 13","Network Monitoring and Defense",{"family":29,"item":34,"code":35,"title":36,"together":9},"17","Control 17","Incident Response Management",{"family":29,"item":38,"code":39,"title":40,"together":9},"8","Control 8","Audit Log Management",{"family":42,"item":43,"code":44,"title":44,"together":9},"itil","overview","ITIL",{"family":46,"item":43,"code":47,"title":48,"together":9},"mitre-attack","ATT&CK","MITRE ATT&CK",{"family":50,"item":51,"code":52,"title":53,"together":9},"nist-800-53","au-6","AU-6","Audit Record Review, Analysis, and Reporting",{"family":50,"item":55,"code":56,"title":57,"together":9},"ir-4","IR-4","Incident Handling",{"family":50,"item":59,"code":60,"title":61,"together":9},"si-3","SI-3","Malicious Code Protection"]