<![CDATA[in one of @adamshostack's (excellent) books i highlighted a lot but recent threads here about this topic and saw it scroll by:]]>in one of @adamshostack's (excellent) books i highlighted a lot but recent threads here about this topic and saw it scroll by:

> First, turn on automatic update on everything, most especially devices, operating systems, and web browsers. The updates that engineers ship often address security problems that can be exploited automatically. If your vendor mixes functionality changes with security fixes, complain loudly.

]]>https://board.circlewithadot.net/topic/d24dff93-b27f-4e81-92b0-264bf15cf5c8/in-one-of-@adamshostack-s-excellent-books-i-highlighted-a-lot-but-recent-threads-here-about-this-topic-and-saw-it-scroll-byRSS for NodeMon, 25 May 2026 14:49:41 GMTSat, 16 May 2026 16:50:29 GMT60<![CDATA[Reply to in one of @adamshostack's (excellent) books i highlighted a lot but recent threads here about this topic and saw it scroll by: on Sat, 16 May 2026 17:09:07 GMT]]>the latest update may just as likely be a malicious payload. so how are we supposed to stay current and safe? scheduled patch cycles? sandboxes? these all require automation and the fastest paths would use inference, which is another path for malicious software to get involved.

]]>https://board.circlewithadot.net/post/https://soc.kvet.ch/users/emory/statuses/116585355490965938https://board.circlewithadot.net/post/https://soc.kvet.ch/users/emory/statuses/116585355490965938Sat, 16 May 2026 17:09:07 GMT<![CDATA[Reply to in one of @adamshostack's (excellent) books i highlighted a lot but recent threads here about this topic and saw it scroll by: on Sat, 16 May 2026 17:07:32 GMT]]>now i would argue the opposite position.

]]>https://board.circlewithadot.net/post/https://soc.kvet.ch/users/emory/statuses/116585349263343712https://board.circlewithadot.net/post/https://soc.kvet.ch/users/emory/statuses/116585349263343712Sat, 16 May 2026 17:07:32 GMT