Category: InfoSec

Source: Help Net Security

Author: Mirko Zorz

URL: https://www.helpnetsecurity.com/2025/07/09/why-cybersecurity-friction/

1. ONE SENTENCE SUMMARY: Internal cybersecurity friction, driven by complex tools, unclear processes, and cautious culture, hinders security teams more than external threats.

2. MAIN POINTS:

3. Security teams face internal friction due to tool sprawl, unclear ownership, and rigid processes.

4. Disconnected tools require analysts to switch dashboards, slowing response and increasing alert fatigue.

5. Approval-heavy workflows delay incident response, risking critical containment windows.

6. Lack of context in access requests leads to repeated clarification cycles, wasting time.

7. Ambiguities in responsibilities cause delays and confusion during handoffs between teams.

8. Caution culture discourages initiative, pushing decisions upward and reducing overall team agility.

9. Burnout and normalized inefficiencies lower morale and inhibit improvement efforts.

10. Evolving security roles now require balancing protection with enabling business growth.

11. Integration and shared data visibility can reduce both friction and risk.

12. Clear thresholds and role clarity empower faster, accountable responses without sacrificing security.

13. TAKEAWAYS:

14. Streamlining tools and processes can significantly improve security team efficiency and morale.

15. Trust frameworks and role clarity reduce the need for excessive approvals.

16. Culture change must promote speed and responsibility, not just caution.

17. Shared visibility and system-level enforcement reduce manual friction.

18. Internal delays are a silent threat that can undermine security more than external attacks.

Source: Unit 42

Author: Haizhou Wang, Ashkan Hosseini, Ashutosh Chitwadgi

URL: https://unit42.paloaltonetworks.com/lnk-malware/

1. ONE SENTENCE SUMMARY: Attackers increasingly exploit Windows LNK files, using varied techniques such as exploits, malicious file execution, and embedded scripts for malware delivery.

2. MAIN POINTS:

3. Malicious LNK samples surged from 21,098 in 2023 to 68,392 in 2024.

4. LNK files act as shortcuts to other files, applications, or folders in Windows.

5. Attackers abuse LNK flexibility, disguising malware as legitimate files to trick users.

6. Four types of LNK malware: exploit execution, malicious file execution, in-argument scripts, and overlay content execution.

7. Most malicious LNK files contain LINKTARGET_IDLIST, RELATIVE_PATH, or COMMAND_LINE_ARGUMENTS structures.

8. Common system targets abused include powershell.exe, cmd.exe, rundll32.exe, conhost.exe, and mshta.exe.

9. COMMAND_LINE_ARGUMENTS can embed malicious scripts directly within LNK files.

10. Overlay content execution techniques involve find/findstr, mshta, or PowerShell commands.

11. CVE-2010-2568 vulnerability is notably exploited using corrupted LNK binaries.

12. Users should carefully inspect LNK file properties, especially target paths, to detect malware.

13. TAKEAWAYS:

14. Windows users should be cautious and verify LNK files’ properties before execution.

15. Cybersecurity teams must understand LNK malware techniques to enhance defenses.

16. Palo Alto Networks products offer protection against various LNK-based attacks.

17. Overlay content execution techniques are increasingly used to hide malicious payloads.

18. Awareness of common system targets and malware structures significantly aids malware detection.

Source: Help Net Security

Author: Help Net Security

URL: https://www.helpnetsecurity.com/2025/07/04/ntlm-relay-attacks/

ONE SENTENCE SUMMARY: NTLM relay attacks remain prevalent, simple to execute, and effective at compromising Active Directory environments, requiring proactive mitigation strategies.

MAIN POINTS:

1. NTLM relay attacks exploit authentication exchanges without needing password cracking or weak passwords.
2. Relay attacks often combine with authentication coercion techniques like Printer Bug or PetitPotam.
3. SMB servers, LDAP/LDAPS services, and ADCS web enrollment are primary NTLM relay targets.
4. SMB relay attacks can grant attackers access to sensitive shares and enable lateral movement.
5. LDAP relay attacks exploit unenforced LDAP signing and channel binding on domain controllers.
6. ADCS web enrollment relay attacks enable attackers to impersonate victims using malicious certificates.
7. Microsoft is introducing mitigations such as enforced SMB signing and LDAP sealing starting Windows Server 2025.
8. NTLM is still widely used due to legacy software hard-coded to use it instead of Kerberos.
9. Default configurations often leave older Windows environments highly vulnerable to relay attacks.
10. Enforcing signing, channel binding, and regularly evaluating environments are critical for defense.

TAKEAWAYS:

1. NTLM relay attacks remain a significant threat, commonly used in real-world attacks.
2. Authentication coercion makes relay attacks viable anytime, not relying on victim-initiated authentication.
3. Default configurations leave many organizations vulnerable; proactive changes are necessary.
4. Upcoming Windows Server 2025 security defaults will help, but organizations shouldn’t wait to implement mitigations.
5. Regular security evaluations, SMB/LDAP signing enforcement, and channel binding are essential defensive practices.

Source: BleepingComputer

Author: Sergiu Gatlan

URL: https://www.bleepingcomputer.com/news/security/cisco-removes-unified-cm-callManager-backdoor-root-account/

1. ONE SENTENCE SUMMARY: Cisco has patched a critical backdoor vulnerability (CVE-2025-20309) in Unified Communications Manager allowing attackers remote root access.

2. MAIN POINTS:

3. Cisco Unified CM had a critical backdoor root account vulnerability identified as CVE-2025-20309.

4. The vulnerability arises from static, default credentials used during development and testing.

5. CVE-2025-20309 affects Unified CM and SME Engineering Special releases 15.0.1.13010-1 to 15.0.1.13017-1.

6. Exploitation allows unauthenticated attackers root-level remote access to affected systems.

7. No workarounds exist; admins must upgrade or apply the CSCwp27755 security patch.

8. Cisco provided indicators of compromise to assist detection and response efforts.

9. Successful exploitation creates log entries under /var/log/active/syslog/secure accessible by admins.

10. Cisco previously experienced similar backdoor vulnerabilities in IOS XE, DNA Center, and Emergency Responder.

11. Earlier this year, Cisco patched similar issues in Smart Licensing Utility and IOS XE devices.

12. No current evidence indicates active exploitation or available proof-of-concept code online.

13. TAKEAWAYS:

14. Immediately apply the Cisco-provided security patch or upgrade to mitigate this severe vulnerability.

15. Regularly check logs at /var/log/active/syslog/secure for suspicious root user activities.

16. Stay vigilant for security advisories from Cisco regarding hardcoded credential vulnerabilities.

17. Maintain awareness that even reputable products may have hidden backdoor accounts.

18. Prioritize patch management to rapidly address high-severity vulnerabilities in critical infrastructure.

Source: Secure by Choice

Author: Sarah Aalborg

URL: https://securebychoice.com/blog/108175-we-see-what-we-expect-and-miss-what

ONE SENTENCE SUMMARY: Forensic investigations are impacted by cognitive biases like confirmation and anchoring, requiring deliberate strategies to mitigate their influence effectively.

MAIN POINTS:

1. Forensic analysis, despite being data-driven, is heavily influenced by cognitive biases.
2. Human brains naturally create stories, filtering new data through existing assumptions.
3. Confirmation bias leads investigators to focus only on evidence supporting initial theories.
4. Anchoring bias causes undue emphasis on the first piece of evidence discovered.
5. A Guardian-cited study found forensic experts influenced by contextual biases reached differing conclusions.
6. Bias affects even highly experienced experts, often without their awareness.
7. Explicitly naming biases can help teams recognize and counteract their impact.
8. Conducting pre-mortems encourages consideration of alternative hypotheses before deep investigation.
9. Introducing fresh perspectives can reduce anchoring effects and improve investigative accuracy.
10. Tracking multiple scenarios and reflecting on assumptions enhances learning and accuracy in forensics.

TAKEAWAYS:

1. Recognize that even expert investigators are vulnerable to cognitive biases.
2. Explicitly acknowledging biases helps mitigate their negative impact.
3. Regularly question initial assumptions and entertain multiple theories.
4. Seek input from individuals not influenced by initial investigative contexts.
5. Reflecting systematically on investigative processes improves future outcomes.

Source: Blog RSS Feed

Author: Gilad David Maayan

URL: https://www.tripwire.com/state-of-security/critical-security-risks-facing-cobol-mainframes

1. ONE SENTENCE SUMMARY: COBOL remains vital in global enterprise systems yet faces significant security risks requiring proactive measures and modern security practices.

2. MAIN POINTS:

3. COBOL is deeply embedded in critical global systems like banking, insurance, and government.

4. Legacy COBOL systems face growing cybersecurity threats due to outdated security configurations.

5. COBOL’s stability and batch processing efficiency sustain its widespread use in mainframe environments.

6. Industries relying on COBOL include finance, insurance, government, retail, manufacturing, and healthcare.

7. Dynamic SQL in COBOL applications can lead to SQL injection attacks if input isn’t sanitized.

8. Legacy communication protocols (FTP, TN3270) transmit sensitive data without encryption, increasing vulnerability.

9. Weak authentication and outdated access control methods expose COBOL systems to unauthorized access risks.

10. Privilege escalation vulnerabilities arise from poor application logic, misconfigurations, or insecure scripts.

11. COBOL applications often lack adequate input validation and error handling, risking exploitation.

12. Best practices include regular code reviews, pentesting, proactive patching, developer training, and compliance adherence.

13. TAKEAWAYS:

14. Regularly review and update legacy COBOL code to address potential vulnerabilities.

15. Employ comprehensive mainframe penetration testing to identify hidden security weaknesses.

16. Implement proactive patch management strategies to protect against known threats.

17. Provide ongoing developer training on secure coding practices specific to COBOL environments.

18. Ensure strict adherence to industry compliance standards for maintaining secure COBOL-based systems.

Source: BleepingComputer

Author: Lawrence Abrams

URL: https://www.bleepingcomputer.com/news/security/microsoft-365-direct-send-abused-to-send-phishing-as-internal-users/

1. ONE SENTENCE SUMMARY: A phishing campaign exploiting Microsoft 365’s Direct Send feature bypasses security measures, targeting numerous U.S. organizations to steal credentials.

2. MAIN POINTS:

3. Phishing attacks exploit Microsoft 365’s Direct Send, bypassing standard authentication and email security protocols.

4. Direct Send enables unauthenticated email delivery via a tenant’s smart host, designed for devices like printers.

5. Microsoft advises using Direct Send only if companies can properly manage and configure email servers.

6. Varonis MDDR team discovered the phishing campaign targeting over 70 U.S. organizations since May 2025.

7. Attackers primarily target financial services, manufacturing, healthcare, insurance, construction, and engineering sectors.

8. Phishing emails impersonate voicemail or fax notifications, including PDF attachments branded with company logos.

9. PDFs instruct victims to scan QR codes, redirecting them to fake Microsoft login pages for credential theft.

10. Attackers utilize PowerShell scripts sent from external IP addresses to send internal-looking emails.

11. Emails fail SPF, DKIM, DMARC checks yet pass through security as trusted internal traffic via smart host.

12. Microsoft introduced “Reject Direct Send” setting in Exchange Admin Center to mitigate these phishing attacks.

13. TAKEAWAYS:

14. Carefully evaluate if Direct Send is necessary, and if not, disable or restrict it immediately.

15. Enable “Reject Direct Send” in Exchange Online to prevent unauthorized internal-looking emails.

16. Implement strict DMARC policies (p=reject) to block unauthorized internal domain usage.

17. Train employees regularly to recognize and avoid phishing attempts, especially those involving QR codes.

18. Regularly monitor internal email traffic for signs of spoofing or abnormal behavior.

Source: Windows Incident Response

Author: Unknown

URL: http://windowsir.blogspot.com/2025/06/program-execution-follow-up-pt-ii.html

ONE SENTENCE SUMMARY: Validating program execution through multiple correlated data sources is crucial, rather than assuming artifacts alone indicate successful execution.

MAIN POINTS:

1. ShimCache and AmCache artifacts alone do not reliably indicate successful program execution.
2. Security Event Log (4720) confirms successful creation of user accounts beyond just command execution.
3. “net user” commands may inaccurately imply new account creation when only password is changed.
4. Application Event Log MsiInstaller records confirm actual installations via msiexec.exe.
5. Application Pop-up or Windows Error Reporting logs can show unsuccessful program launches.
6. Antivirus logs indicate if threats were successfully quarantined or if malware execution continued.
7. WMI-Activity/5861 event logs confirm successful creation of malicious WMI event consumers.
8. Parsing Objects.DATA file can verify if malicious event consumers persist in the WMI repository.
9. Correlating multiple data sources provides a system-level confirmation of actual execution outcomes.
10. Validating findings prevents incorrect decisions and ensures accurate resource allocation.

TAKEAWAYS:

1. Always validate artifact interpretations with complementary log sources.
2. Single artifacts alone rarely indicate successful execution; cross-reference multiple logs.
3. Consider transient and persistent data sources when confirming program execution.
4. Build timelines from multiple event logs to accurately validate threat actor actions.
5. Ensure your analysis is robust and data-supported, as critical decisions depend on accurate findings.

Source: BleepingComputer

Author: Bill Toulas

URL: https://www.bleepingcomputer.com/news/security/new-citrixbleed-2-netscaler-flaw-let-hackers-hijack-sessions/

1. ONE SENTENCE SUMMARY: Citrix warns of critical “CitrixBleed 2” vulnerabilities affecting NetScaler ADC and Gateway devices, potentially exposing sensitive user data.

2. MAIN POINTS:

3. Citrix disclosed vulnerabilities CVE-2025-5777 and CVE-2025-5349 affecting NetScaler ADC and Gateway devices.

4. CVE-2025-5777 is an out-of-bounds memory read allowing unauthenticated attackers memory access.

5. Vulnerable configurations include Gateway setups like VPN virtual servers, ICA Proxy, CVPN, and AAA servers.

6. Cybersecurity researcher named flaw “CitrixBleed 2” due to similarities with older CitrixBleed vulnerability.

7. Attackers exploiting CVE-2025-5777 could hijack sessions, bypass MFA, and access sensitive credentials.

8. CVE-2025-5349 involves improper access control in NetScaler Management Interface through various IPs.

9. Citrix recommends updating to safe versions: 14.1-43.56, 13.1-58.32, 13.1-NDcPP 13.1-37.235 (FIPS), and 12.1-55.328 (FIPS).

10. Admins should terminate all active ICA and PCoIP sessions after installing patches.

11. End-of-life versions ADC/Gateway 12.1 (non-FIPS) and ADC/Gateway 13.0 will not receive patches.

12. Over 56,500 publicly exposed NetScaler endpoints exist, unclear how many remain vulnerable.

13. TAKEAWAYS:

14. Immediately update NetScaler ADC and Gateway devices to mitigate “CitrixBleed 2” vulnerabilities.

15. Regularly monitor and terminate suspicious ICA and PCoIP sessions post-update.

16. Replace unsupported end-of-life versions promptly to maintain security posture.

17. Assess publicly exposed NetScaler endpoints to prioritize patching vulnerable systems.

18. Leverage automation to simplify and accelerate patch management processes.

Source: Dark Reading

Author: Fahmida Y. Rashid

URL: https://www.darkreading.com/endpoint-security/nist-outlines-real-world-zero-trust-examples

ONE SENTENCE SUMMARY: NIST’s new SP 1800-35 guidance provides practical examples and phased implementation strategies for organizations adopting end-to-end zero-trust architectures.

MAIN POINTS:

1. NIST released SP 1800-35 guidance demonstrating real-world zero-trust architectures using commercial technologies.
2. The guidance includes 19 practical example implementations developed over four years with 24 industry partners.
3. SP 1800-35 builds upon NIST SP 800-207, moving from conceptual to practical ZTA implementation advice.
4. Organizations must customize zero-trust deployments due to their unique network environments and security requirements.
5. Zero-trust architectures continuously evaluate and verify access requests, removing implicit trust in users or devices.
6. Implementing zero trust significantly reduces lateral movement and privilege escalation by malicious actors.
7. NCCoE team installed, configured, and tested each example, providing troubleshooting assistance and best practices.
8. Guidance aligns solutions with NIST Cybersecurity Framework and NIST SP 800-53 standards.
9. Organizations should incrementally adopt foundational elements like identity management and multifactor authentication.
10. Zero trust is an ongoing journey requiring continual adaptation to evolving threats, technologies, and organizational needs.

TAKEAWAYS:

1. Leverage NIST’s practical examples to start customized zero-trust deployments.
2. Begin ZTA implementation with a thorough inventory of existing organizational assets and capabilities.
3. Formulate clear access policies based on least privilege and continuous verification principles.
4. Incrementally implement ZTA components, starting with foundational security solutions.
5. Continuously monitor and evolve zero-trust architectures to address changing threats and business requirements.

Source: BleepingComputer

Author: Sergiu Gatlan

URL: https://www.bleepingcomputer.com/news/security/gitlab-patches-high-severity-account-takeover-missing-auth-issues/

1. ONE SENTENCE SUMMARY: GitLab urgently released patches for critical vulnerabilities allowing account takeover, malicious CI/CD job injections, and denial-of-service attacks.

2. MAIN POINTS:

3. GitLab issued security updates for Community and Enterprise editions 18.0.2, 17.11.4, and 17.10.8.

4. CVE-2025-4278 vulnerability allows attackers to hijack accounts through HTML injection.

5. CVE-2025-5121 flaw permits malicious CI/CD job injection into future project pipelines.

6. CVE-2025-2254 addresses a cross-site scripting vulnerability affecting legitimate user sessions.

7. CVE-2025-0673 fixes a denial-of-service issue involving infinite redirect loops and memory exhaustion.

8. GitLab.com and Dedicated customers already have the security patches applied.

9. GitLab strongly urges immediate upgrades for all self-managed installations.

10. Attackers exploiting CVE-2025-5121 require authenticated access to GitLab Ultimate licensed instances.

11. Recent breaches affected Europcar Mobility Group and Pearson through compromised GitLab repositories.

12. GitLab platform serves over 30 million users, including half of Fortune 100 companies.

13. TAKEAWAYS:

14. Immediately upgrade self-managed GitLab instances to patched versions.

15. Ensure strict authentication and access controls, especially for GitLab Ultimate environments.

16. Recognize the high-value target GitLab represents due to sensitive information in repositories.

17. Regularly monitor GitLab security advisories to respond swiftly to emerging threats.

18. Automate patching processes to streamline security updates and reduce administrative overhead.

Source: The Hacker News

Author: info@thehackernews.com (The Hacker News)

URL: https://thehackernews.com/2025/06/over-80000-microsoft-entra-id-accounts.html

ONE SENTENCE SUMMARY: Attackers exploit TeamFiltration to target Microsoft Entra ID accounts, compromising over 80,000 users via password spraying and enumeration methods.

MAIN POINTS:

1. New ATO campaign named UNK_SneakyStrike targets Microsoft Entra ID user accounts.
2. Attackers leveraged open-source framework TeamFiltration, originally for penetration testing.
3. Over 80,000 user accounts breached across numerous cloud tenants since December 2024.
4. Microsoft Teams API and AWS servers were utilized to perform attacks.
5. Primary attack methods include password spraying, user enumeration, and data exfiltration.
6. Malicious files were uploaded to victims’ Microsoft OneDrive accounts for persistent access.
7. Attack waves originated from geographically dispersed AWS servers to evade detection.
8. Top attacking regions were United States (42%), Ireland (11%), and Great Britain (8%).
9. Attacks occurred in concentrated bursts followed by quiet periods of four to five days.
10. Smaller cloud tenants experienced broad targeting, while larger tenants had selective targeting.

TAKEAWAYS:

1. Security tools intended for protection can be weaponized by attackers.
2. Organizations must monitor for abnormal login attempts and geographic patterns.
3. Regularly review and tighten user account access and permissions in cloud environments.
4. Implement proactive defenses such as multi-factor authentication to counteract password spraying.
5. Remain vigilant about publicly available security frameworks being misused by threat actors.

Source: Rapid7 Cybersecurity Blog

Author: Adam Barnett

URL: https://www.rapid7.com/blog/post/2025/06/10/patch-tuesday-june-2025/

ONE SENTENCE SUMMARY:

Microsoft’s June 2025 Patch Tuesday addresses 67 vulnerabilities, including two notable zero-days and eight critical remote code execution flaws.

MAIN POINTS:

1. Microsoft released patches for 67 vulnerabilities in June 2025 Patch Tuesday update.
2. Only one vulnerability, CVE-2025-33053 (WebDAV RCE), is actively exploited in-the-wild.
3. WebDAV vulnerability exploited by threat actor Stealth Falcon targeting Middle Eastern governments.
4. Windows WebDAV implementation has been deprecated since November 2023, reducing default exposure risk.
5. CVE-2025-33073 in Windows SMB Client is a publicly disclosed elevation of privilege vulnerability.
6. Critical RCE vulnerability CVE-2025-33071 affects Windows KDC Proxy Service with exploitation considered likely.
7. Three Office vulnerabilities (CVE-2025-47162, CVE-2025-47164, CVE-2025-47167) leverage Preview Pane for exploitation.
8. Microsoft 365 Apps for Enterprise patches for critical Office vulnerabilities not yet available.
9. Eight critical remote code execution vulnerabilities were disclosed, requiring immediate attention.
10. Two browser vulnerabilities previously published separately are not included in the June 2025 totals.

TAKEAWAYS:

1. Prioritize patching actively exploited WebDAV vulnerability CVE-2025-33053 immediately.
2. Urgently address critical Windows KDC Proxy vulnerability CVE-2025-33071 on exposed servers.
3. Monitor closely the SMB Client vulnerability CVE-2025-33073 due to public disclosure and potential exploitation.
4. Understand Office Preview Pane vulnerabilities significantly increase exploitation risk.
5. Keep aware of the delayed availability of patches for Microsoft 365 Apps for Enterprise.

Source: Rapid7 Cybersecurity Blog

Author: Chris Boyd

URL: https://www.rapid7.com/blog/post/2025/06/04/rapid7-q1-2025-incident-response-findings/

ONE SENTENCE SUMMARY:

Rapid7’s Q1 2025 report highlights stolen credentials without MFA as the top initial access vector, widespread BunnyLoader malware, and targeted ransomware attacks primarily affecting manufacturing.

MAIN POINTS:

1. Stolen credentials without MFA remain the leading initial access vector, causing 56% of incidents.
2. Exposed RDP services were the initial access vector in 6% but exploited further in 44% of incidents.
3. Vulnerability CVE-2024-55591 in Fortinet appliances widely exploited, enabling attacker control and data exfiltration.
4. Exploited SimpleHelp RMM vulnerabilities (CVE-2024-57726/57727/57728) facilitated ransomware deployment.
5. SEO poisoning via sponsored search ads led directly to malware downloads and ransomware attacks.
6. BunnyLoader malware observed in 40% of incidents, prevalent across nearly all industries.
7. Fake CAPTCHA attacks accounted for half of BunnyLoader malware deployments.
8. Manufacturing was the most targeted industry, involved in over 24% of incidents.
9. Qilin ransomware group actively targeted healthcare, manufacturing, financial sectors through double-extortion attacks.
10. Attackers frequently disabled security tools and backups to prevent recovery post-compromise.

TAKEAWAYS:

1. Implementing MFA remains critical, as attackers consistently exploit unprotected valid credentials.
2. Organizations must secure exposed RDP and RMM tooling to prevent ransomware infections.
3. Be cautious of sponsored search results to avoid SEO poisoning and malware downloads.
4. Strengthen defenses against BunnyLoader malware, particularly fake CAPTCHA and compromised sites.
5. Manufacturing organizations should prioritize securing legacy systems and complex supply chains.

Source: BleepingComputer

Author: Sponsored by Specops Software

URL: https://www.bleepingcomputer.com/news/security/kerberos-as-rep-roasting-attacks-what-you-need-to-know/

ONE SENTENCE SUMMARY: AS-REP Roasting attacks exploit Active Directory accounts without Kerberos pre-authentication, highlighting the critical importance of enforcing strong, secure passwords.

MAIN POINTS:

1. AS-REP Roasting targets Active Directory user accounts lacking Kerberos pre-authentication.
2. Normally, Kerberos pre-authentication securely transmits timestamps encrypted with user password hashes.
3. Attackers exploit disabled pre-authentication, capturing AS-REP responses containing Ticket Granting Tickets (TGT).
4. Criminals extract passwords from TGTs offline, often using brute-force techniques.
5. Tools like Rubeus or Impacket facilitate AS-REP Roasting attacks.
6. Cybersecurity agencies identify AS-REP Roasting among top Active Directory threats.
7. Verizon reports stolen credentials involved in nearly half of data breaches.
8. Organizations must identify vulnerable accounts using specialized detection scripts.
9. Monitoring specific Windows Event IDs (4625, 4768, 4738, 5136) can detect ongoing attacks.
10. Strong, uncompromised passwords and strict password policies significantly mitigate AS-REP Roasting risks.

TAKEAWAYS:

1. Enforce Kerberos pre-authentication on Active Directory accounts to prevent AS-REP Roasting.
2. Monitor and log key Windows security events to detect malicious activity promptly.
3. Limit privileges and isolate accounts that must bypass Kerberos pre-authentication.
4. Implement robust, compliant password policies to protect accounts against brute-force attacks.
5. Regularly audit passwords against breached databases to maintain security and compliance.

Source: GitHub

Author: unknown

URL: https://github.com/msdirtbag/MDEAutomator

1. ONE SENTENCE SUMMARY: MDEAutomator is a modular, serverless Azure Function and PowerShell-based solution streamlining endpoint management, incident response, threat hunting, and custom detection synchronization for Microsoft Defender for Endpoint (MDE).

2. MAIN POINTS:

3. Provides bulk automation of response actions, live response commands, and threat indicator management.

4. Utilizes Azure Functions (Dispatcher, Orchestrator, Profiles, TIManager, AutoHunt, CDManager) for endpoint orchestration.

5. Supports multi-tenant operations using User Managed Identity and App Registration federation.

6. Enables bulk threat hunting using KQL queries via Microsoft Graph API, exporting results to Azure Storage.

7. Allows bulk synchronization of Custom Detections with Azure Storage, including backup capabilities.

8. Offers convenient uploading/downloading of files and scripts to/from endpoints and Azure Storage.

9. Implements Python/Flask-based GUI hosted in Azure App Service with Entra ID authentication.

10. Provides cmdlets for essential operations such as device isolation, application execution restriction, and forensic package collection.

11. Supports advanced security practices including signed PowerShell scripts via Azure Trusted Signing.

12. Has an estimated monthly Azure cost of approximately $210 USD.

13. TAKEAWAYS:

14. MDEAutomator significantly enhances Defender endpoint management through serverless automation and orchestration.

15. Customizable PowerShell modules simplify complex MDE tasks like live response and threat indicator management.

16. Multi-tenant readiness and federated identity options support scalable deployments.

17. Advanced security measures like signed scripts and App Service authentication are strongly recommended.

18. Comprehensive automation of custom detections and threat hunting greatly improves operational efficiency.

Source: Medium

Author: James Booth

URL: https://jmspbooth.medium.com/1-1-identity-governance-in-a-zero-trust-world-1ca5b58c4b8c

ONE SENTENCE SUMMARY: Identity governance operationalizes Zero Trust security by continuously managing user access, entitlements, and lifecycle events through automated, policy-driven controls.

MAIN POINTS:

1. Most breaches occur due to unmanaged identities, orphaned accounts, and excess permissions.
2. Zero Trust requires continuous verification of identity and entitlements in real-time.
3. Identity governance ensures accurate user verification through robust identity proofing methods.
4. Centralized directories with policy-as-code enforce consistent access controls across all systems.
5. Decentralized identity (DIDs) enhances trust through cryptographically verified credentials.
6. Automated lifecycle management rapidly revokes permissions when users change roles or leave.
7. Non-human identities (bots, containers) require similar rigorous lifecycle governance controls.
8. Conditional access dynamically evaluates real-time risk signals to adjust access levels immediately.
9. Governance-as-code provides auditable, immutable records of entitlement changes and compliance.
10. Effective identity governance significantly reduces breach probability and audit overhead costs.

TAKEAWAYS:

1. Implement identity proofing and high-assurance authentication to enhance trust in user identities.
2. Leverage centralized, policy-as-code IAM systems for consistent and secure access management.
3. Adopt automated processes for join-move-leave events to mitigate risks from orphaned accounts.
4. Include non-human identities in governance frameworks to address all possible security threats.
5. Use decentralized identity and conditional access to build resilience against single points of failure.

Source: The Hacker News

Author: info@thehackernews.com (The Hacker News)

URL: https://thehackernews.com/2025/06/critical-cisco-ise-auth-bypass-flaw.html

ONE SENTENCE SUMMARY: Cisco issued critical patches addressing a static credential vulnerability in cloud-based Identity Services Engine deployments, allowing unauthorized access.

MAIN POINTS:

1. Cisco released patches for critical vulnerability CVE-2025-20286 in Identity Services Engine (ISE).
2. The flaw has a critical CVSS severity rating of 9.9 out of 10.
3. Issue stems from improperly generated static credentials in cloud deployments.
4. Affected platforms include AWS, Microsoft Azure, and Oracle Cloud Infrastructure (OCI).
5. Exploitation allows attackers access to sensitive data and limited administrative tasks.
6. Vulnerability affects cloud-based Primary Administration nodes only; on-premises nodes are safe.
7. Credentials are identical across deployments of same Cisco ISE release and cloud platform.
8. Exploit could allow attacker to disrupt services or change system configurations.
9. Proof-of-concept exploit exists, but no evidence of malicious exploitation yet.
10. Cisco recommends restricting administrator traffic or performing a factory reset as mitigation.

TAKEAWAYS:

1. Immediately apply Cisco’s security patches to affected cloud deployments.
2. Restrict administrative access to trusted sources to mitigate potential exploits.
3. Consider resetting Cisco ISE passwords using provided command, despite configuration reset risks.
4. Regularly monitor for unusual activity, given the availability of proof-of-concept exploit.
5. Evaluate and plan migration strategies to unaffected software versions or on-premises nodes.

Source: Varonis Blog

Author: Daniel Miller

URL: https://www.varonis.com/blog/cloud-telemetry

1. ONE SENTENCE SUMMARY: Telemetry enables proactive cloud security by analyzing real-time data to detect anomalies, strengthen defenses, and respond swiftly to threats.

2. MAIN POINTS:

3. Telemetry collects real-time data to monitor cloud environments and detect security threats proactively.

4. AWS CloudTrail logs API calls, aiding in auditing, compliance, and detecting unauthorized access.

5. Azure Monitor analyzes telemetry data, integrating with Azure Security Center for enhanced threat detection.

6. Google Cloud Audit Logs track resource actions to detect suspicious activities and ensure policy compliance.

7. Telemetry helps identify unusual patterns, like spikes in API calls signaling potential breaches.

8. Detailed telemetry records support auditing and demonstrate compliance with regulatory requirements.

9. Continuous telemetry monitoring improves security posture by addressing vulnerabilities in real-time.

10. Automation of telemetry monitoring ensures prompt detection and response to threats.

11. Integrating telemetry data with SIEM enhances comprehensive threat detection and security visibility.

12. Challenges like data volume, quality, and integration complexity require effective data management strategies.

13. TAKEAWAYS:

14. Utilize cloud provider tools (AWS CloudTrail, Azure Monitor, GC Audit Logs) for robust telemetry.

15. Continuously monitor telemetry data to proactively detect and respond to threats.

16. Integrate telemetry solutions with SIEM systems for comprehensive security insights.

17. Automate telemetry monitoring processes to improve efficiency and threat response speed.

18. Address telemetry challenges with efficient data management, validation, and standardized integration practices.

Source: Active Countermeasures

Author: Faan Rossouw

URL: https://www.activecountermeasures.com/threat-hunting-c2-over-https-connections-using-the-tls-certificate/

ONE SENTENCE SUMMARY: The article discusses techniques for threat hunting command and control (C2) activity hidden within HTTPS connections using TLS certificates.

MAIN POINTS:

1. Threat actors often hide C2 traffic within encrypted HTTPS connections.
2. TLS certificates can provide valuable indicators for detecting malicious activities.
3. Legitimate certificates are sometimes misused by attackers for C2 communications.
4. Anomalies in TLS certificate metadata help identify suspicious HTTPS connections.
5. Certificate attributes like issuer, validity period, and domain can indicate malicious usage.
6. Automated tools can analyze TLS certificates efficiently to detect threats.
7. Inspecting certificates is essential for effective threat hunting practices.
8. TLS certificate fingerprinting helps identify known malicious infrastructure.
9. Monitoring certificate issuance patterns can uncover malicious actors’ infrastructure.
10. Properly implemented TLS certificate inspection enhances cybersecurity posture.

TAKEAWAYS:

1. Leverage TLS certificate metadata analysis to detect hidden C2 channels.
2. Pay attention to unusual certificate attributes to identify potential threats.
3. Integrate certificate inspection into existing threat hunting methodologies.
4. Automate TLS certificate monitoring to efficiently spot anomalies.
5. Maintain updated threat intelligence on TLS certificate misuse for effective detection.

Source: Dark Reading

Author: unknown

URL: https://www.darkreading.com/cyber-risk/you-dont-need-red-team

ONE SENTENCE SUMMARY: Attack path mapping, a collaborative and cost-effective offensive security methodology, offers broader coverage and better educates teams compared to traditional red-team exercises.

MAIN POINTS:

1. Most red-team exercise requests are redirected due to client readiness, budget, or understanding issues.
2. Attack path mapping involves collaboration between offensive operators and internal security SMEs.
3. Traditional red-team tests identify only the simplest paths rather than providing comprehensive coverage.
4. Attack path mapping starts by defining critical business objectives and potential attacker entry points.
5. Working transparently with internal experts accelerates reconnaissance and better maps attack paths.
6. Cloud-native environments demand collaborative testing due to advanced identity management protections.
7. Realistic scenarios such as compromised DevOps roles offer better insights into actual security risks.
8. Purple teams, while beneficial, often sacrifice realism by overly focusing on endpoint security tests.
9. Automated purple team exercises effectively assess detection capabilities but overlook deeper threats.
10. The suggested collaborative methodology provides more comprehensive insights and better overall value.

TAKEAWAYS:

1. Collaborative methodologies provide broader security coverage than traditional stealth-based red teams.
2. Engaging internal experts significantly accelerates offensive security assessments and enriches outcomes.
3. Realistic attacker scenarios better address genuine security threats than standard isolated test cases.
4. Cloud security assessments benefit significantly from granting testers higher visibility and realistic privileges.
5. Carefully evaluate whether a traditional red-team exercise truly meets your organization’s security needs.

Source: The Red Canary Blog: Information Security Insights

Author: Sam Straka

URL: https://redcanary.com/blog/security-operations/conditional-access-cisco-duo/

1. ONE SENTENCE SUMMARY: This blog compares Microsoft’s Entra ID Conditional Access and Cisco’s Duo Adaptive Access Policies, highlighting their similarities, differences, and integration possibilities.

2. MAIN POINTS:

3. Duo primarily provides MFA layered over existing identity solutions, unlike full IAM platforms like Microsoft.

4. Duo policies can be globally applied or targeted per application/user group, similar to Entra ID.

5. Duo enforces MFA by default, with conditional bypass options for trusted scenarios.

6. Device compliance checks in Duo use certificates or health apps, comparable to Entra ID Intune integration.

7. Duo’s user interface for granular device policy rules is user-friendly and intuitive.

8. Duo offers geolocation and trusted network conditions similar to Entra ID’s named locations.

9. Duo introduced Risk-Based Authentication (RBA) in 2023, focusing on anomalies during MFA steps.

10. Duo doesn’t directly block legacy authentication, relying instead on primary authentication systems.

11. Duo excels at enforcing device health and compliance checks for sensitive resource access.

12. Duo integrates as a third-party MFA provider with Entra ID Conditional Access via custom controls.

13. TAKEAWAYS:

14. Duo is ideal for organizations looking primarily for strong MFA and device health checks.

15. Microsoft Entra ID offers deeper integration with device management and broader risk evaluation signals.

16. Duo’s RBA effectively addresses MFA fatigue and anomalous sign-in behaviors.

17. Combining Duo with Entra ID provides comprehensive conditional access coverage but introduces complexity.

18. Advanced conditional access features in both solutions require higher-tier licensing plans.

Source: BadSuccessor: Unpatched Microsoft Active Directory attack enables domain takeover | CSO Online

Author: unknown

URL: https://www.csoonline.com/article/3992456/badsuccessor-unpatched-microsoft-active-directory-attack-enables-domain-takeover.html

ONE SENTENCE SUMMARY:

Researchers discovered a critical vulnerability named “BadSuccessor” in Windows Server 2025 Active Directory allowing attackers full domain compromise without needing privileged accounts.

MAIN POINTS:

1. Researchers identified “BadSuccessor,” a new vulnerability in Windows Server 2025 Active Directory.
2. The flaw exploits Delegated Managed Service Accounts (dMSA), intended to mitigate Kerberoasting attacks.
3. Attackers can impersonate any user, including domain administrators, through manipulated dMSA account attributes.
4. Microsoft rated the issue moderately severe, not immediately urgent, despite researchers’ strong disagreement.
5. dMSA accounts inherit permissions of superseded service accounts through migration processes lacking proper validation.
6. Key Distribution Center (KDC) mistakenly grants privileges based solely on easily manipulated account attributes.
7. Attackers can exploit CreateChild permissions on Organizational Units (OUs) to create malicious dMSA accounts.
8. Unprivileged users can arbitrarily set attributes to falsely indicate completed migrations, gaining unauthorized privileges.
9. Attackers can extract encrypted passwords included in the KERB-DMSA-KEYPACKAGE structure of session tickets.
10. Akamai released a PowerShell script and monitoring guidelines for organizations until Microsoft provides an official patch.

TAKEAWAYS:

1. Immediately restrict CreateChild permissions to trusted administrators.
2. Use Akamai’s provided PowerShell script to audit current AD environments for vulnerable permissions.
3. Implement recommended SACLs to log suspicious dMSA creations and attribute modifications.
4. Regularly monitor for unusual TGTs containing KERB-DMSA-KEYPACKAGE structures.
5. Advocate for urgent internal review of AD permissions despite Microsoft’s moderate severity rating.

Source: Dark Reading

Author: Denny LeCompte

URL: https://www.darkreading.com/cyber-risk/hidden-cybersecurity-risks-mergers-acquisitions

1. ONE SENTENCE SUMMARY: Ignoring cybersecurity during mergers and acquisitions exposes businesses to hidden vulnerabilities, compliance issues, and costly security breaches post-acquisition.

2. MAIN POINTS:

3. Mergers involve inheriting digital footprints including endpoints, credentials, and hidden security vulnerabilities.

4. Cybersecurity is frequently neglected in due diligence, creating substantial risk post-acquisition.

5. IT integration chaos often leads to insufficient access control and outdated credential management.

6. Legacy systems from acquired companies pose significant cybersecurity threats if not assessed.

7. Employees are vulnerable to phishing scams during transitions, increasing insider threat risks.

8. Inadequate cybersecurity training can result in sensitive data leaks and breaches post-merger.

9. Regulatory and compliance mismatches between companies can create serious legal and financial liabilities.

10. Comprehensive cybersecurity audits must evaluate identities, compliance histories, and past breaches.

11. Companies should promptly standardize security policies and adopt modern, cloud-native security solutions.

12. Proactive cybersecurity integration during mergers is essential to protect reputation, trust, and financial value.

13. TAKEAWAYS:

14. Prioritize cybersecurity due diligence alongside financial and operational assessments.

15. Enforce strict access control policies and revoke outdated credentials immediately post-acquisition.

16. Conduct thorough audits of legacy IT systems and address incompatibilities proactively.

17. Implement cybersecurity awareness and anti-phishing training programs early in the merger process.

18. Align quickly with the strictest compliance standards from both companies to mitigate regulatory risks.

Source: Help Net Security

Author: Mirko Zorz

URL: https://www.helpnetsecurity.com/2025/05/22/tim-grieveson-thingsrecon-asset-inventory-gaps/

ONE SENTENCE SUMMARY: Tim Grieveson emphasizes ongoing automated asset discovery, cross-functional collaboration, addressing overlooked blind spots, and context-driven risk prioritization.

MAIN POINTS:

1. Asset inventory should be ongoing, automated, and integrated with business context, not a one-time project.
2. Communicating inventory issues openly with stakeholders is crucial for managing associated risks.
3. Leveraging existing endpoint agents, cloud providers, DNS records, and procurement systems enhances initial visibility.
4. Implementing dedicated continuous discovery tools significantly improves security visibility and asset context.
5. Clearly defining inventory scope and categorizing assets prevents critical elements from being overlooked.
6. Asset inventory requires collaboration across security, IT operations, development, network, and business teams.
7. Biggest blind spot is relying solely on documentation without validating actual live assets.
8. Commonly overlooked assets include subdomains, public APIs, third-party integrations, and misconfigured DNS services.
9. Asset discovery must integrate closely with vulnerability management, threat detection, and CMDB systems.
10. Contextual information (exposure, business-criticality, usage) is essential for accurate asset risk prioritization.

TAKEAWAYS:

1. Shift asset inventory mindset from periodic audits to continuous, automated discovery.
2. Build cross-functional teams to maintain comprehensive asset visibility across organizational silos.
3. Regularly validate documented assets against actual infrastructure to prevent blind spots.
4. Expand discovery to external, third-party, and edge assets beyond traditional network boundaries.
5. Prioritize risk based on asset exposure, criticality, and business context rather than just severity scores.