Reddit, Inc.’s Post

𝗖𝗗𝗞 𝗢𝘂𝘁𝗮𝗴𝗲 - 𝗔𝘂𝘁𝗼𝗺𝗼𝘁𝗶𝘃𝗲 𝗗𝗲𝗮𝗹𝗲𝗿𝘀𝗵𝗶𝗽𝘀 To my customers and contacts that may be using CDK Global products, here's a Reddit threat with some updates direct from customers posting their communications with CDK. https://lnkd.in/gacpXxua #cdkglobal #msp #cybersecurity  

The Ethical social engineering neighbour getting your password. Wi-Fi is for all to use unless it's secured. Make sure you secure your home Wi-Fi you never know who's accessing your network. Put a password on it. 😂 #cybersecurity #wifisecurity #socialengineering

Cybersecurity professionals, what are your thoughts on this? The CMMC assessors may be the hardest to convince of this kind of thinking. Join the debate on this unclassified CUI case for M365 commercial ITAR on Reddit. Check out the link here: https://lnkd.in/gBACrZSK #Cybersecurity #CMMC #M365 #ITAR #Debate

text: Crucial alert: Protecting against malicious open-source packages Here's why this topic is vital for every developer and security pro: Open-source vulnerabilities are skyrocketing, threatening countless projects. Traditional defenses often fall short against sophisticated package threats. Understanding what works

It's over. There will only be two eras in cybersecurity and identity management: 1. Before Deep-Live-Cam (Aug 9th, 2024) 2. After Deep-Live-Cam (Aug 9th, 2024) This will fundamentally transform cybersecurity in work from home and any remote setting. Zoom can no longer be trusted. Social engineering attacks will overwhelm all current authentication systems. Adoption of deep biometrics, and zero knowledge sessions (ZKI > PKI) will accelerate. BioTone ZKI is poised to lead the way! https://lnkd.in/gWbriicU

For those that think about DFARS 7012, 800-171, and CMMC this post is for you. Good recap of the September CMMC AB townhall. #cybersecurity #CMMC #DOC

CTEM Thoughts by /u/yurychemerkin via reddit.com: search results - cybersecurity ([Global] Security Breach) URL: https://ift.tt/XI2N38H Continuous Threat Exposure Management (CTEM) is a cybersecurity strategy that focuses on identifying, assessing, and mitigating risks within an organization's digital environment through continuous monitoring and enhancement of security posture. CTEM is not a single tool or technology but a set of processes and capabilities that involve a five-step program or framework, which includes scoping, discovery, prioritization, validation, and mobilization CTEM is a proactive and continuous approach that differs from traditional vulnerability management by being proactive rather than reactive, focusing on a wide range of threats, incorporating existing security measures, and utilizing advanced simulation tools for validation A. Tools and Technologies CTEM leverages a variety of tools and technologies to support its implementation and improvement. These tools aid in the discovery, assessment, prioritization, validation, and mobilization stages of the threat management cycle. Key tools and technologies include CAASM (Cyber Asset Attack Surface Management), EASM (External Attack Surface Management), EM (Exposure Management), RSAS (Red Team Automation Systems).These tools provide visibility into network segments, security controls, threat types, and tactics/techniques, and are crucial for identifying and analyzing an organization's attack surface, which includes external, internal, and cloud environment B. Methodology The five stages of the CTEM program are: · Scoping: Defining the initial exposure scope, considering business-critical assets, and taking an adversarial approach rather than just focusing on known vulnerabilities (CVEs). · Discovery: Actively seeking out and identifying potential vulnerabilities using tools like automated scanners, manual testing, and penetration testing. · Prioritization: Focusing on the most significant threats that could impact the business and prioritizing remediation efforts accordingly.· Validation: Assessing the effectiveness of remediation operations and ensuring that vulnerabilities are properly addressed. · Mobilization: Operationalizing the CTEM findings and defining communication standards and documented cross-team workflows C. Best Practices Best practices for prioritizing threats during CTEM implementation include: · Stakeholder Engagement: Engage with various stakeholders, including IT, legal, compliance, and business units, to understand their specific requirements and concerns · Regular Updates: Establish a regular schedule for updates and patches to strengthen the network against current known threats and preemptively address potential future threats · Incident Response Plan: Design an effective incident response plan to promptly respond to threats. The plan should be kept updated in line with emerging threats · Optimized R...

CTEM Thoughts by /u/yurychemerkin via reddit.com: search results - cybersecurity ([Global] Data Breach) URL: https://ift.tt/XI2N38H Continuous Threat Exposure Management (CTEM) is a cybersecurity strategy that focuses on identifying, assessing, and mitigating risks within an organization's digital environment through continuous monitoring and enhancement of security posture. CTEM is not a single tool or technology but a set of processes and capabilities that involve a five-step program or framework, which includes scoping, discovery, prioritization, validation, and mobilization CTEM is a proactive and continuous approach that differs from traditional vulnerability management by being proactive rather than reactive, focusing on a wide range of threats, incorporating existing security measures, and utilizing advanced simulation tools for validation A. Tools and Technologies CTEM leverages a variety of tools and technologies to support its implementation and improvement. These tools aid in the discovery, assessment, prioritization, validation, and mobilization stages of the threat management cycle. Key tools and technologies include CAASM (Cyber Asset Attack Surface Management), EASM (External Attack Surface Management), EM (Exposure Management), RSAS (Red Team Automation Systems).These tools provide visibility into network segments, security controls, threat types, and tactics/techniques, and are crucial for identifying and analyzing an organization's attack surface, which includes external, internal, and cloud environment B. Methodology The five stages of the CTEM program are: · Scoping: Defining the initial exposure scope, considering business-critical assets, and taking an adversarial approach rather than just focusing on known vulnerabilities (CVEs). · Discovery: Actively seeking out and identifying potential vulnerabilities using tools like automated scanners, manual testing, and penetration testing. · Prioritization: Focusing on the most significant threats that could impact the business and prioritizing remediation efforts accordingly.· Validation: Assessing the effectiveness of remediation operations and ensuring that vulnerabilities are properly addressed. · Mobilization: Operationalizing the CTEM findings and defining communication standards and documented cross-team workflows C. Best Practices Best practices for prioritizing threats during CTEM implementation include: · Stakeholder Engagement: Engage with various stakeholders, including IT, legal, compliance, and business units, to understand their specific requirements and concerns · Regular Updates: Establish a regular schedule for updates and patches to strengthen the network against current known threats and preemptively address potential future threats · Incident Response Plan: Design an effective incident response plan to promptly respond to threats. The plan should be kept updated in line with emerging threats · Optimized Risk ...

So the "xz backdoor" (that was only discovered because a nerd at Microsoft was profiling SSH comms as he noticed it was lagging by 500ms) - it's not likely many people were compromised. BUT, it does showcase a real security vulnerability angle - open source maintainers who are bad actors (this doesn't mean they've got dodgy acting skills, but are people with malicious intent). With so much of the world relying on open source software and free help from programmers, how much of the code we use daily contains malicious code? 🤔 Simple info on the xz backdoor: https://lnkd.in/eX_FW6ps #opensource #programming #software #cybersecurity

Rooted another neat machine from VulnLab. Like with "Breach" in "Media", you get the initial foothold through NTLM phishing (Greenwolf's ntlm_theft is your friend). Privesc is pretty cool, there is a way to abuse symlinks and create a junction to get a PHP web shell uploaded to the webroot. From there it's a pretty straight-forward process to enable privileges with FullPowers.exe and then abusing DCOM with our favorite "potato" to get a system shell. I recommend it, check it out. #vulnlab #hacking https://lnkd.in/e_jQqfuR