TL: DR
You don’t have to be an expert, but it helps – Team82 State of XIoT 1H22
Only one Too Long; Did Read post this week, The State of XIoT report for 1H 2022 by Claroty’s Team82. The content and analysis of this report was uneven. There is a ...
I wanted to like this report, but … – Fortinet Global Threat Landscape Report 1H 2022
The Thursday edition of ‘Too Long; Did Read’ focuses on Fortinet’s Global Threat Landscape Report for the first half of 2022. In my experience, 7-8 weeks to go from data collection to ...
Hidden Gems Amongst Too Much Text – Unit 42 Cloud Threat Report
My first report for this week’s ‘Too Long; Did Read’ is titled “Identity Access Management: The First Line of Defense” by Unit 42 and Prisma Cloud. The report is moderate in length ...
451 Group on API Trends – Spot On, for the Intended Audience
Today’s post for ‘Too Long; Did Read’, is a review of the 2022 API Security Trends Report, written by Dan Kennedy of the 451 Group/S&P for noname Security. Going forward I’ll add ...
On being critical of industry reports in security
One last thing: A good editor is your best friend when it comes to writing! And like any good friend, they may sometimes tell you your baby is ugly. At least you ...
’50 Shades of Blue’ or ‘Red Hot Mess’ from CyberTheory
Who should read this? Marketing and content creation teams might gain some insight from this report. It is primarily aimed at people trying to connect to CISOs after all. I would suggest ...
Great information in need of polish from Meta
While the content of the report is excellent, it needs more copy editing and better layout. It's clearly a labor of love by the technical teams at Meta, rather than a marketing ...
PwC Survey – Decent report, too little analysis
I’m repurposing the initialism ‘TL: DR’ to mean ‘Too Long: Did Read’. I have been writing industry reports since 2015 and reading them far longer, which gives me a wealth of experience ...
