#ssblogwatch search results

:@PyPI attackers used compiled code to evade detection. Possibly first attack to take advantage of .PYC files. @ReversingLabs’ reverse engineering team led by Karlo Zanki (pictured) spotted the tactic. In this week’s #SSBlogwatch we round up reax right: reversinglabs.com/blog/pypi-hack…


3/ Naturally, it’s dividing opinions. As usual, in this week’s #SSBlogwatch we’re not going to tell you what to think. For @ReversingLabs@SecuredSoftware: reversinglabs.com/blog/white-hou…


Googlers will be protected from themselves. In what’s described as a pilot program, they’ll lose internet access at work and/or root privs. The idea is to stop break-ins. In this week’s #SSBlogwatch we try not to imagine the horror. For @ReversingLabs: reversinglabs.com/blog/no-net-fo…


Last month’s @MSItweets data theft causing panic: Extremely sensitive signing #keys have been found among the leaked data. If nothing else, there are important lessons to learn. In this week’s #SSBlogwatch we lock up our secrets. For @ReversingLabs: reversinglabs.com/blog/msi-uefi-…


Bug allowed bad actor to manipulate URLs: 💭Dev should avoid consecutive object references and add entropy. 💭Ops should detect attacks and shut ’em down or tarpit them. In this week’s #SSBlogwatch we ask what Brown can do for us? For @ReversingLabs: reversinglabs.com/blog/hackers-b…


#Passkeys looks almost ready for prime time. Apple and Google are supporting it — and being interoperable. Isn’t it time your dev team did, too? In this week’s #SSBlogwatch we get below the surface blather. For @ReversingLabs: reversinglabs.com/blog/passkeys-…


:@MITREcorp’s top three are exactly the same as last year. Combined, just those three account for about half the problems. #CWE #1, #4, #7 and #17 are #MemorySafety bugs. In this week’s #SSBlogwatch we point the finger at C/C++. For @ReversingLabs: reversinglabs.com/blog/heres-mit…


Googlers will be protected from themselves. In what’s described as a pilot program, they’ll lose internet access at work and/or root privs. The idea is to stop break-ins. In this week’s #SSBlogwatch we try not to imagine the horror. For @ReversingLabs: reversinglabs.com/blog/no-net-fo…


:@MITREcorp’s top three are exactly the same as last year. Combined, just those three account for about half the problems. #CWE #1, #4, #7 and #17 are #MemorySafety bugs. In this week’s #SSBlogwatch we point the finger at C/C++. For @ReversingLabs: reversinglabs.com/blog/heres-mit…


Bug allowed bad actor to manipulate URLs: 💭Dev should avoid consecutive object references and add entropy. 💭Ops should detect attacks and shut ’em down or tarpit them. In this week’s #SSBlogwatch we ask what Brown can do for us? For @ReversingLabs: reversinglabs.com/blog/hackers-b…


#Passkeys looks almost ready for prime time. Apple and Google are supporting it — and being interoperable. Isn’t it time your dev team did, too? In this week’s #SSBlogwatch we get below the surface blather. For @ReversingLabs: reversinglabs.com/blog/passkeys-…


:@PyPI attackers used compiled code to evade detection. Possibly first attack to take advantage of .PYC files. @ReversingLabs’ reverse engineering team led by Karlo Zanki (pictured) spotted the tactic. In this week’s #SSBlogwatch we round up reax right: reversinglabs.com/blog/pypi-hack…


Last month’s @MSItweets data theft causing panic: Extremely sensitive signing #keys have been found among the leaked data. If nothing else, there are important lessons to learn. In this week’s #SSBlogwatch we lock up our secrets. For @ReversingLabs: reversinglabs.com/blog/msi-uefi-…


3/ Naturally, it’s dividing opinions. As usual, in this week’s #SSBlogwatch we’re not going to tell you what to think. For @ReversingLabs@SecuredSoftware: reversinglabs.com/blog/white-hou…


No results for "#ssblogwatch"
No results for "#ssblogwatch"
Loading...

Something went wrong.


Something went wrong.


United States Trends