Jarmo Lahtiranta retweeted
You can catch @mikko and @tomituominen interviewing @halvarflake in their "Gentlemen Hackers" series.
Insightful, educational.. Worth it..
youtube.com/watch?v=rf_lN754…
Jarmo Lahtiranta retweeted
It's kinda been raised, but its nuts that (according to Mandiant/M-Trends) in 2025:
- vulnerabilities/exploits are the most frequently observed initial vector;
- the top 4 exploited vulns belong to security vendors.
What are we doing here? 🤯😱
Jarmo Lahtiranta retweeted
In security engineering, strictness and paranoia correlate with incompetence.
Easier to say ‘no’ than to deeply understand the use case and find middleground.
Jarmo Lahtiranta retweeted
Me reverse engineering: Haha fuck yeah!!! Yes!!
Me engineering: Well this fucking sucks. What the fuck.
Jarmo Lahtiranta retweeted
It's Baaaaaack!!
Our Credit Card Canarytokens are out of beta and on your Canarytoken servers..
- Grab one;
- Stash it somewhere "safe";
- We will notify you if it's ever used!
Read more about it at blog.thinkst.com/2024/12/its…
Jarmo Lahtiranta retweeted
Another CA fails the turing test, issuing a MITM certificate. This highlights ongoing issues with underperforming CAs. I’ve shared my thoughts on the incident and what to expect next. unmitigatedrisk.com/?p=908
Jarmo Lahtiranta retweeted
Is Tether getting added to M2?
The Fed contemplates…
New #FEDSNote: An Update to Measuring the U.S. Monetary Aggregates: federalreserve.gov/econres/n… #EconTwitter
Jarmo Lahtiranta retweeted
Bingo.
The idea that there's some sort of meaningful foundational separation between "security" and "IT" in an organization is not only nonsensical but practically very destructive of efforts to implement good security.
Jarmo Lahtiranta retweeted
r3b00ts law number 9001:
Just because it could happen, does not mean you are obliged to defend against it!
Just because you could defend against it, doesn't mean the return on investment is worth it!
It is ok to accept risk! It is a choice! You just need to be comfortable with the outcomes of that choice!
Jarmo Lahtiranta retweeted
Concerning trend in AppSec (well really in web dev):
During the boom of modern frontend web frameworks (Angular, React, etc.) - we saw a dramatic drop in traditional AppSec issues like XSS.
I've long said modern web frameworks have done more for AppSec than any DAST/SAST tool ever did.
Example: dangerouslySetInnerHTML() is what a dev would have to write in React to turn OFF XSS protections that are there by default.
Now I'm seeing a shift AWAY from those web frameworks, back to more stripped down web components.
Turns out React is too slow and overly complex for many projects.
This is most likely a correct decision, but I'm already seeing it where devs are rewriting functionality that currently exists in React, but don't realize some of the built in security guardrails exist, and reintroduce vulns.
Unfortunately, most DAST companies didn't survive the previous framework boom, they all pivoted to ASM, got sold for parts, or are surviving on legacy customers with piles of Java.
The tech never was able to crawl and find issues in the new frameworks.
I'm not sure we'll ever get back to 2010 state of AppSec bugs everywhere, but I'd keep an eye on this trend.
Jarmo Lahtiranta retweeted
When I discussed quitting Google to do a Phd, my manager, Steve Cheng, gave me the advice of "6 shots": Doing something meaningful usually takes about 5 years and we are productive for roughly 30 years. That gives you 6 attempts. So pick each one carefully and give it your best.
Jarmo Lahtiranta retweeted
Please share this far and wide. As far and wide as you can. NIST Password Guidelines for 2024 are in the process of being updated.
This is a HUGE pet-peeve of mine (when vendors in particular are still operating like its 2017 and keep changing passwords every 60 days, STOP DOING THIS, it's outdated and has been shown to put you MORE at risk than less -- NIST explains why it does in this document, meticulously outlining user behavior**) so I'm sharing this in the hopes all of you will pass it along to your bosses.
The Special Publication series governing passwords is SP 800-63 "Digital Identity Guidelines".
The 2024 version is 800-63-4.
Here: pages.nist.gov/800-63-4/
The companion docs are also on that link. They are 800-63A, 800-63B and 800-63C. These are different documents for different scenarios in play at your org.
The previous update was in2020.
The changes in the 2020 version from the 2017 version were numerous but one of them was that the password verification method should NO LONGER require passwords be changed at specific intervals (i.e. every 60 days) but in the following circumstances instead:
1. After a breach/compromise
2. User request
2024 repeats this and adds a bunch more guidlines but here is a screenshot of page 13 of the new 800-63-4 (note the # 4 after it) which outlines how your systems should now and moving forward, be handling passwords.
This goes for Active Directory, too. All your systems which have passwords should align with these guidelines provided there isn't another standard or framework you must adhere to which overrules this.
Most frameworks, however, have moved away from arbitrary password resets and complexity rules.
**We cybersec researchers and hackers use wordlists from breaches in a variety of different ways. Hackers use them in tooling to crack passwords whereas researchers use breach dumps to see the kinds of passwords users are creating and the psychology behind them.
Using complexity rules gets you the user psychology of:
Password1
Password2
and so on
Use phrasing instead and allow for spaces, which is important. Humans type phrases with spaces. They also mention phish-resistant methods and most vendors are on-board with MS going to be turning off all Legacy Auth next month, across all free accounts and tenancies.
I'm so excited for the new changes!
Ok I'm off my soapbox.
Share the love! Thank you!
Jarmo Lahtiranta retweeted
Reports flooding in about pager batteries exploding across Lebanon targeting Hezbolah operatives.
The articles are claiming "Malware" and cyberattacks might be the cause overheating the batteries.
Security experts disagree... Let's dig in:
Jarmo Lahtiranta retweeted
CapLoader 1.9.7 Released!
🆔 Community ID's for flows
🔁 Retransmission ratios
👾 Detection of malware C2 protocols
🐣 Decapsulation of Teredo, GTP-U and more...
h/t @NetcowboyDK, @naranek and @ckreibich
netresec.com/?b=2499359
Jarmo Lahtiranta retweeted
fucking naming the anonymous inventor of Bitcoin after the CIA is not something the actual CIA would do, but it’s DEFINITELY something the NSA would do LOL
Jarmo Lahtiranta retweeted
The apparent conclusion—uncomfortable if not unthinkable for free marketeers—is that MBA/finance thinking and decision-making is not just not helpful but actively hostile and destructive to running a successful, functional company.
Jarmo Lahtiranta retweeted
Let's talk about some of the security features of the new @Raspberry_Pi RP2350, because they are 🔥🧵



































