I was in a intercontinental flight few weeks ago and when everyone was sleeping my wife was able to open Instagram and scroll the feed, while other websites were not accessible.
I did not have a PC with me, but I immediately guessed about they are doing filtering based on SNI.
Appliances like Allot or Sandvine are in this market since more than a decade.
Antennas are really black magic: optimizing an antenna requires stocastich method like genetic algorithms, simulated annealing, etc.
Moreover if you want to model the radiation patterns and the electrical characteristics you need to use finite element calculation methods.
So, you need a lot of computation power as antenna are not a problem that can be solved in a closed form.
Source: I almost burnt my PC on simulating a dipole array while studying for the antennas course at the university
I have a customer facing role, then it's easy to get questions about details that I don't know from the customers.
My approach is easy: always being very transparent. I can say "I am not 100% sure, then I will verify with my colleagues and with R&D and let you know" or just "I don't know right now, but I am taking notes and let you know ASAP". This approach also helps me to ask the right questions to the customer, just to understand what the customer wants.
I was on the other side for years and I hate when consultants try to avoid the questions or give me foggy replies.
Almost 10 years ago I created couple of Twitter bots that can tweet like the leaders of two populisti Italian party. The quality of the tweets was sometimes not the best, but usually decent. It was impressive how many people starts following them in few weeks.
In a corporate environment you must use only the company DNS internal resolver and they are the only one that should go outside on port 53.
This is a basic security measure to detect and block every attempt of DNS tunnelling or exfiltration
This means that the security department is not doing a good job: things like iodine can be detected easily by a NGFW or by an analysis on DNS logs. This is a quite basic security posture.
Back when I was using it similarly to the other poster (say, 15 years ago) that wasn't the case. It's still a great litmus test of security posture today.
Just using DNS for data exfiltration, in general, is usually pretty fruitful. I wrote a "live off the land" data exfil script for Windows once, using the certutil and nslookup commands to base64 encode data and ship it out to my off-site DNS server.
I'll have to try it against a Palo Alto NGFW sometime and see what alarms I trip. I honestly never thought to try.
MFA is quite more complex to implement, especially if legacy applications are involved. Applying a basic DNS security monitoring is not hard, you can even implement with few policies on the border FW and something like an ELK stack.
The most difficult part is implementing an appropriate process
I always considered the ergonomic of async/await not really ergonomical and hard to debug. I really like, indeed, the go approach: using goroutines, channels and waitgroups is powerful and easy.
reply