Raluca Mihu

🇮🇹 We’re bringing the expert-level stack exploit development class to Rome, Italy for the first time in history! 🇮🇹 You don’t want to miss out on this unique opportunity to take the first of our 2 world-renowned classes on exploit development for Windows. ⭐️ Our classes are an amazing investment in your future. The content will definitely broaden your offensive cybersecurity skills and put yourself in the drivers seat of your career ⭐️ Just to set the expectations straight: We’re not selling boxes, pdf files, videos. We’re only doing real classes, in person, lead by Peter Van Eeckhoutte himself. He has been working in the field of exploit development since 2005 and teaching classes since 2011. At the same time, you can still learn at your own pace. In fact, you’ll leave the class with: ✅ An unprecedented understanding of the inner workings and mechanics. We won’t tell you to “just do this or that”, but you’ll understand exactly “why”. ✅ The courseware is quite detailed and verbose ✅ Investment protection; Just to indicate how much we care about your education, we include FREE access to a post-training support system. You can ask questions at any time and we’ll be more than happy to guide you into the right direction. Yes, even years after you took one of our classes. Sign up now for our class in Rome, or check out our schedules page for other timings/locations: https://lnkd.in/e-GhbBW

55

1 commentaar

Did you know that “the majority of ransomware victims in the Netherlands had no backup” (source https://lnkd.in/eGMQkNiY)? A recent report from the Digital Trust Center in the Netherlands highlights the importance of not only having good preventative security measures in place, but also reliable backup solutions. Don't let your business fall victim to ransomware attacks. Ensure that you educate your people to recognize suspicious behavior, implement the right solutions to protect your valuable assets, don’t compromise on patches and please have a solid backup strategy in place to protect your valuable data and maintain business continuity. Outcomes of such reports keep surprising me. There are so many successful ransomware attacks known already and we are already talking about cyber resilient back-ups.. why are the basics of simple business continuity not well arranged and tested? Ask for help if it is complicated to do it alone, but take the necessarily steps, I would say!   #ransomware #cybersecurity #backup #businesscontinuity #cyberresilience

18

1 commentaar

Do you have a cyber incident that you must report according to the NIS2 rules? ⚠ You can now obtain a special incident form on our website! (also in Dutch/French) ➡ https://lnkd.in/eQA5RfSb ⬅ This form is designed to help you comply with reporting requirements quickly and accurately. 🔝 This way you ensure that your organization complies with legislation and remains protected against possible risks. Go to our website to request the form and be prepared! 👍 #nis2 #networksecurity #informationsecurity #nis #ciso #cybersecurity

3

𝑨 𝒒𝒖𝒊𝒄𝒌 𝒉𝒊𝒈𝒉𝒍𝒊𝒈𝒉𝒕 𝒐𝒇 𝒔𝒐𝒎𝒆 𝒏𝒆𝒘 𝒕𝒉𝒊𝒏𝒈𝒔 𝑰'𝒎 𝒉𝒊𝒓𝒊𝒏𝒈 𝒇𝒐𝒓... All with small to medium sized boutique IAM consultancies, or consultancies with IAM consulting departments 🆒😎 🆔 𝐀𝐧𝐭𝐰𝐞𝐫𝐩 𝐚𝐫𝐞𝐚 (at least once a week) - 𝐒𝐞𝐧𝐢𝐨𝐫 𝐂𝐲𝐛𝐞𝐫𝐀𝐫𝐤 𝐂𝐨𝐧𝐬𝐮𝐥𝐭𝐚𝐧𝐭𝐬 - Dutch speaking preferred Don't need to be a CyberArk pro - seniority, consultancy capability & of course an interest to become a CyberArk pro are key! 🆔 𝐂𝐨𝐥𝐨𝐠𝐧𝐞 𝐚𝐫𝐞𝐚 (once a month) - 𝐒𝐞𝐧𝐢𝐨𝐫 𝐈𝐀𝐌 𝐂𝐨𝐧𝐬𝐮𝐥𝐭𝐚𝐧𝐭𝐬 - German speaking essential Project management, consulting, implementation and more (no heavy software dev though if that's you), 𝐭𝐨𝐨𝐥 𝐚𝐠𝐧𝐨𝐬𝐭𝐢𝐜 but have done projects in One identity, Sailpoint, Omada, Beta Systems... 🆔 𝐑𝐞𝐦𝐨𝐭𝐞 𝐟𝐢𝐫𝐬𝐭 𝐢𝐧 𝐆𝐞𝐫𝐦𝐚𝐧𝐲 - 𝐒𝐞𝐧𝐢𝐨𝐫 𝐓𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐈𝐀𝐌 𝐂𝐨𝐧𝐬𝐮𝐥𝐭𝐚𝐧𝐭 - German speaking essential Strong coding needed, ideally frontend with Angular & One Identity Manager (or One Login etc) ... 𝐭𝐡𝐞𝐫𝐞'𝐬 𝐦𝐨𝐫𝐞! Live on planet earth? Curious about your options in IAM? (especially consulting) You and I should have a chat! 😎🤞🏻 ... you know where to find me, and if not for you, our referral reward for introducing your friends awaits 😜 #identityandaccessmanagement #iam #consulting

22

3 commentaren

Join me and Vincent van Dijk MSc on 8th of May for an open discussion about NIS2 implementation and its minimal measures 👇 (Link in description) What are the minimal requirements of upcoming NIS2 directive? How do you interpret them? What can you do stay compliant and secure at the same time? ***** 😎 Hi! I’m Andrei ⚔️ Cybersecurity consultant and pentester 🛡️ Security tips, strategies & best practices 💥 Finding vulnerabilities in your applications 👿 One step ahead hackers Like what I post? 🔔 Share, Follow & turn on notifications #cybersecurity #webinar #nis2 #risk

18

1 commentaar

Mission accomplished, Offensive X has ended. Now it’s time for me, Marek and Konrad to relax. But first, a quick recap of what I've learned from the conference. 1️⃣ A solid approach to Red Teaming exercises with a sprinkle of TIBER framework presented by Pieter Ceelen from (Outflank). 2️⃣ Apparently CREST created OWASP Verification Standard which is an accreditation for companies providing security assessments. This came straight from Tom Brennan during his keynote. 3️⃣ Bug hunting & exploit development was, is and will be hard(er). This is my conclusion from talk by Patroklos Argyroudis, Zisis Sialveras and Chariton Karamitas. (BTW. Good luck on your BH talk Zisis!) 4️⃣ Challenges with vulnerability disclosure within automotive industry are actually pretty similar to what we already know. So even though there is experience that could be gathered same mistakes are made. Thanks to Yashin Mehaboobe for this talk. And last, but not least we've had a chance to interact with Sofia by Hanson Robotics Limited which is a robot whose brain is powered by #AI. (Of course we immediately asked problematic questions and quickly got banned, hehe.) Thanks again to Athena and the entire team for this great event. See you next year! ☺️

69

1 commentaar

#CyCatz #cybersecurity How I Hacked the Dutch Government: Exploiting an Innocent Image for Remote Code Execution More..https://rb.gy/gkdu1d #cyberawareness #cyberattack #breaches #databreaches #cybercrime #darkwebmonitoring #SurfaceWebMonitoring #mobilesecurity #emailsecurity #vendorriskmanagement #BrandMonitoring #security #information #bugbounty #rce

3

Maybe you missed it, but the Dutch Government published their NIS2 readiness update on October 17th. TLDR: They're not ready. Like most of the EU countries. (I know. We're all shocked by the news. Didn't see that one coming.) Technically, NIS2 has came into force on October 17th. But the Dutch implementation legislation is far from ready. How far? They expect it in Q3 2025. Maybe. In the meantime though, while reporting and registration requirements are not in force (and they can't be, without the legal basis), NCSC is encouraging a kind of "voluntary compliance", and that the reporting of incidents should be done via the NCSC website. In fairness, NCSC does also offer some assistance for monitoring and for reporting, to be decided on a case-by-case basis. But without a strict legal requirement, and with some reporting requirements already covered by other regulations (such as GDPR's 72 hours for data breaches), I expect organizations will take a very careful look at balancing these new "voluntary compliance" recommendations, with the potential negative impacts. Legal departments, by their nature and mandate, will always recommend the option that exposes their companies to the least minimal legal risk. Unless NCSC can better articulate how will those concerns be alleviated, or provide better incentives to balance them out, I don't expect many organizations to take them up on the current offer. Which is a bit unfortunate, as NCSC on the whole does a pretty good job, and one of the main advantage of reporting to NCSC should be the sharing of IOC's and threat info with other organizations, to help them defend better. But between hypothetical cyberdefense benefits, and hypothetical legal or market repercussions, most organizations will prioritize the latter. https://lnkd.in/eUekjK-g

9

1 commentaar

I have updated my specifications for an HSM-based European Digital Identity (EUDI) wallet I discussed in my previous post: https://lnkd.in/emmZPmX2. In the update I have addressed the comments I got including those from Sander Dijkhuis. I have also indicated more precisely the WSCA role distinguishing it from other (less trusted) Wallet Provider roles such as the front-end sitting between the wallet and the WSCA providing basic internet security. The specifications roughly consist of three parts. First eight security objectives are derived from regulations and standards referred to in the eIDAS 2.0 regulation including eIDAS implementation regulation 2015/1502. These objectives include *verifiable* sole control (a.k.a. Transaction Transparency). The second part is a specification of a basic implementation of an HSM-based EUDI wallet using standard (PKCS#11) meeting the security objectives. The third part is a specification of an *advanced* implementation of an HSM-based EUDI wallet comprising of three modest PKCS#11 instruction extensions. In the update I have added a small addition (Algorithm 9) to the third PKCS#11 instruction extension (on the use of the EN 419221-5 Authorization Data) which yields a remarkable and significant improvement: the HSM (or Cryptographic Module in EN 419221-5 speak) and not the WSCA is ultimately in charge of validating the correctness of the user PIN. That is, the HSM also blocks the PIN when a certain threshold is exceeded. The latter uses the standard EN 419221-5 Authorization Failure Counter approach. I think this is a significant improvement as it provides protection against online brute-forcing of the user PIN even in the extreme situation the attacker has compromised the Wallet Provider, the WSCA and the user wallet (but not the HSM). I think that this further simplifies allowing the WSCA to be implemented as a hardened service instead of as an HSM firmware module which has tremendous implementational and cost benefits. Note that by the design and its use of zero knowledge proofs the user PIN is truly personal and not known by the Wallet Provider, the WSCD or the WSCA just like with a regular smartcard.

60

6 commentaren

🚨 Security Advisory: Important CVEs Disclosed 🚨 Hi Envoy Community, We would like to inform you about the following Common Vulnerabilities and Exposures (CVEs) identified in Envoy: 🔒 CVE-2024-45807: oghttp2 crash on OnBeginHeadersForStream 🔒 CVE-2024-45808: Malicious log injection via access logs 🔒 CVE-2024-45806: Potential manipulation of x-envoy headers from external sources 🔒 CVE-2024-45809: JWT filter crash in the clear route cache with remote JWKs 🔒 CVE-2024-45810: Envoy crashes for LocalReply in HTTP async client 🔧 Resolutions Coming Soon: These issues will be addressed in the following Envoy releases: - v1.31.2 - v1.30.6 - v1.29.9 - v1.28.7 🔗 Release Information: The updates will be available on our Releases Page starting today. 📖 Documentation: For detailed guidance, please refer to our Envoy Documentation. 🔄 Upgrade Recommendation: We strongly encourage all users to update to the latest versions of Envoy to ensure security and stability. 🔍 Ongoing Improvements: A pull request addressing these vulnerabilities has been initiated on the main branch. Thank you for your attention and continued support. ♻ REPOST this to help other Envoy users stay on top of Envoy News. #EnvoyProxy #Kubernetes #Security #CVE #DevOps #CloudNative #OpenSource #CyberSecurity

6

Understanding Cybersecurity Dependencies in Modern Infrastructures If you have been affected by the outage (travel, banking, services or work) ... so sorry. In today’s interconnected digital landscape, cybersecurity is not just about protecting individual systems but also about understanding and managing the intricate web of dependencies that exist between various services. These dependencies can significantly impact the security posture of an organization, making it crucial to have a comprehensive approach to cybersecurity. Cyber dependencies refer to the relationships and interconnections between different components, processes, and entities within a cybersecurity ecosystem. These dependencies can be categorized into several types, including informational, operational, and systemic dependencies. With the proliferation of cloud services, microservices architectures, and third-party integrations, the number of dependencies has increased exponentially. This complexity makes it difficult to map and understand all the interconnections, leading to potential blind spots in security assessments. Cyber attackers are increasingly sophisticated and often exploit these dependencies to launch multi-vector attacks. Conducting thorough risk assessments that include mapping out all dependencies and understanding their potential impact on the overall security posture is essential. Implementing continuous monitoring solutions to detect and respond to threats in real-time is crucial. Leveraging threat intelligence helps stay informed about emerging threats and vulnerabilities that could affect dependent systems. Establishing stringent security requirements for vendors and third-party services is vital. Regularly auditing and assessing their security practices ensures they meet the organization’s standards. Designing systems with resilience and redundancy in mind, including implementing failover mechanisms and backup solutions, ensures that critical services can continue to operate even if a dependent system is compromised. Understanding and managing cyber dependencies is a critical aspect of modern cybersecurity. As organizations continue to adopt new technologies and integrate with various services, the complexity of these dependencies will only increase. By adopting a comprehensive approach that includes risk assessment, continuous monitoring, robust incident response, vendor management, and resilience planning, organizations can better protect themselves against the evolving threat landscape and ensure the security and integrity of their digital assets. #CyberSecurity #InfoSec #DataProtection #NetworkSecurity #CloudSecurity #ITSecurity #DataBreach #Privacy #RiskManagement #ThreatIntelligence #CyberThreats #SecurityAwareness #CyberDefense #CyberAttack #SecurityManagement #DigitalSecurity #SecurityStrategy #TechTrends #TechNews #Innovation

6

Day 61: I never Tried mssqlclient from impacket until today( i used to use sqsh) and it is really amazing and time saving tool try it During your MSSQL pentest. https://lnkd.in/eYth2N4M

14

2 commentaren

🚨Dolibarr: Security Flaw in Payment Module🚨 In #Dolibarr versions before 19.0.2 a low severity vulnerability CVE-2024-34051 was detected. This flaw allows attackers to execute harmful scripts through the "facid" parameter on the payment card page. Stay informed and learn how to protect your data by reading more about this vulnerability here: https://lnkd.in/dEyfmHKK. #vulnerability #security #hossted

1

A zero-day being exploited right now - CVE-2024-30040. Recommend to test, approve and apply patches ASAP. In the meantime, be extra vigilant of attachments - "Typically, users are deceived into interacting with malicious files, which might be delivered via email or instant messaging". https://lnkd.in/eZr_uq8x #zeroday #exploit #patch

13

NAS and SOHO router devices are the worst in terms of security (open door for APT groups). These scary reminders keep coming. Shall we finally take action on it as an industry?

10

Merge Approved! 🥳 I was recently able to give a small addition to the great toolset Dirk-jan Mollema has provided to our community for assessing Azure, https://lnkd.in/eg9Mr-2Z. These changes came after encountering a hardened Azure environment on a client assessment where obtaining Azure tokens in the organization was restricted almost exclusively to authorized browsers. With necessity being the muse of ingenuity, I worked with my team to make the best use of the access we had and perform collections once we had exfiltrated Single Page Application refresh tokens. I will eventually come up with a blog post to help explain how to leverage these changes in more detail. Anyone wanting to learn more about Azure and what it means when someone gets their hands on access and refresh tokens should check out SpecterOps and Dirk-jan's Azure courses. These taught me a large portion of what I now know and use for our client work. https://lnkd.in/eGgjFnWe https://lnkd.in/e_cfqcBz

97