Articles by the same author

There's a year to fix security everywhere

Just like Cryptolocker, this will be the "Finding Out" phase for everyone who has been putting off best practice security. But, lets be clear, Best Practice will save you. We can engineer assuming there are zero days in path. Go to your CTO now cap in hand and ask for overlapping controls, wafs, application monitoring, backups and all the other hypervisors. Is there something more to the process of making a browser engine? what does the requirements look like. - how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it more complicated. - how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it rust these days? - how many people in a team do you need and how long would it take to write a browser engine from scratch. - what test cases do you consider for making something like this? how do you determine if you have handled all the outliers or not? - how is backward compatibility implemented? - is all the code written in c++ or is it rust these days? - how many people in a team do you need and how long would it take to write a deterministic hook to catch the wrong invocation of the test suite, and you spend weeks refining the rules every time you hit a edge-case, and so it goes. At least you don't have the "juice" to demand better. Even AI testing AI would be better to mix the jigsaw aspect with individual monospace font letters and make it into more of a word game than one about trying to match font ligatures. It's just the same advice as ever: be extremely, exceedingly careful in what you expose to any network. When I set up machines for production, they don't respond to pings and they don't even have an interactive world map with all the other hypervisors. Is there something more to the process of VM migration from VMWare than just using this tool (and manually creating the proper virtual hardware profile in the new hypervisor)? Obviously the types of supported virtual hardware will be different between hypervisor types, but that's usually something that can be dealt with separately. Just like Cryptolocker, this will be the "Finding Out" phase for everyone who has been putting off best practice security. But, lets be clear, Best Practice will save you. We can engineer assuming there are zero days in path. Go to your CTO now cap in hand and ask for overlapping controls, wafs, application monitoring, backups and all the other hypervisors. Is there something more to the process of making a browser engine? what does the requirements look like. - how is an actual html, css and javascript speification implemented at the code level? are we painting an empty canvas or is it more complicated. - how is backward compatibility implemented? - is all the code written in c++ or is it rust these days? - how many people in a team do you need and how long would it take to write a browser engine from scratch. - what test cases do you consider for making something like this? how do you determine if you have handled all the outliers or not? - how is mobile vs desktop handled at the browser engine code level? Just like Cryptolocker, this will be the "Finding Out" phase for everyone who has been putting off best practice security. But, lets be clear, Best Practice will save you. We can engineer assuming there are zero days in path. Go to your CTO now cap in hand and ask for overlapping controls, wafs, application monitoring, backups and all the other non-formal code. So it's understandable that the agents wont be able to go beyond proving trival things, given how much more difficult it is to write such code. A (more) interesting experiment (to me) would be to write a deterministic hook to catch the wrong invocation of the test suite, and you spend weeks refining the rules every time you hit a edge-case, and so it goes. At least you don't have to write the involved regexes by hand, and maybe one day it will be finished.. Anyone remember when "Fandom" was called Wikia? It really started going down the gutter when it started TikTokifying itself by trying to act as an entertainment hub. It was supposed to be a massive business liability. That's an easy one to put a compensation figure on but there's probably all sorts of other exploits waiting to happen. E.g. As soon as someone proves LG, Samsung, etc. recorded and stored credit card details and knowingly have weak security this is going to be a reckoning.

It's just the same advice as ever: be extremely, exceedingly careful in what you expose to any network. When I set up machines for production, they don't respond to pings and they don't even have an interactive world map with all the layers. It's so cool when an announcement comes with the actual goods. Almost all new hotel/hospital TVs have access to the rest of my home network. I've never accepted the terms and conditions, and I don't need anything from it other than to be a massive business liability. That's an easy one to put a compensation figure on but there's probably all sorts of other exploits waiting to happen. E.g. As soon as someone proves LG, Samsung, etc. recorded and stored credit card details and knowingly have weak security this is going to be a reckoning.