Software Supply Chain Security

Supply Chain Attack Defence: Three Major Blind Spots Present in All Security Frameworks


A recent study published on Cornell University's arXiv website reveals a worrying fact: even with the implementation of the most comprehensive security frameworks on the market, enterprises still struggle to defend against major supply chain attacks such as SolarWinds, log4j, and XZ Utils. Researchers analysed 73 tasks recommended in 10 well-known software security frameworks (including the US NIST Secure Software Development Framework) and found that all frameworks share common blind spots.

We believe this finding once again proves a core philosophy: simply implementing security frameworks is not enough; a systematic validation process must be established to ensure the practical effectiveness of supply chain security defences.

01 Key Blind Spots in Security Frameworks

The study found that although these frameworks cover 73 best practices, three key mitigation factors are still missing across all of them:

  1. Ensuring the sustainability of open-source software

  2. Using environment scanning tools

  3. Ensuring application partners report their vulnerabilities

It is precisely these blind spots that create opportunities for supply chain attacks like SolarWinds, log4j, and XZ Utils. Next, we will explore how the Saixun Security Metric Validation Platform addresses these blind spots through four key phases.

02 Saixun Security Validation's Four-Phase Validation Method

Phase 1: Do Deployment and Configuration Align with Design?

In the SolarWinds attack, many affected organisations deployed security tools but failed to validate whether these tools were correctly configured and running. Investigations revealed that some victim organisations' security products did not run as designed, or had configuration drift, allowing attackers to remain undetected for long periods.

Saixun Security Validation Method

The core question the Saixun Security Metric Validation Platform focuses on in Phase 1 is: "Do our security products and configurations align with design?"

In this phase, the platform can:

  • Validate that security product deployment conforms to the expected architectural design

  • Confirm the correctness of critical configurations and detect configuration drift

  • Validate that baseline control measures have been correctly implemented

  • Ensure basic functions such as log transmission and time synchronisation are operating normally

This phase directly addresses several foundational defence measures highlighted in the study, including role-based access control, system monitoring, and configuration management, ensuring they are not only deployed but also operating correctly.

Phase 2: Are Security Products Effective in Real-World Scenarios?

After the Log4j vulnerability was exposed, many organisations found that their security tools performed poorly when facing such attacks. Although they passed testing in controlled environments, these tools failed to detect and block attacks when facing real-world scenarios. The issue was that most organisations had never tested the effectiveness of their security products against real-world attack scenarios.

Saixun Security Validation Method

In Phase 2, the core question we focus on is: "Are our security products effective in real-world attack scenarios?"

In this phase, the platform can:

  • Test security products using real-world attack scenarios

  • Assess the detection capabilities of various security products against supply chain attacks

  • Simulate common supply chain attack techniques to validate defensive effectiveness

  • Assess the defensive system's responsiveness to unknown variant attacks

Through these assessments, organisations can understand the actual performance of their security products when facing real-world supply chain attacks, rather than just their theoretical protection capabilities. This directly addresses the missing environment scanning tools highlighted in the study.

Phase 3: Can Correlation Rules Accurately Identify Real Threats?

The XZ Utils attack demonstrated the limitations of single-dimensional detection. Although many organisations deployed multiple security tools and platforms, they lacked effective correlation analysis capabilities to correlate scattered security event logs or audit logs into a complete attack chain. This led to cases where, even if some attack activities were detected, they were not identified as critical threats, not to mention scenarios where security products failed to alert, requiring correlation analysis based on audit logs.

Saixun Security Validation Method

In Phase 3, the core question we focus on is: "Can our correlation rules accurately identify real threats?"

In this phase, the platform can:

  • Identify blind spots and deficiencies in single-product alerting

  • Assess the correlation analysis capabilities of SIEM/SOC

  • Generate Sigma rules using AI technology to supplement detection capabilities

  • Achieve comprehensive correlation analysis based on attack context behaviour

  • Integrate threat intelligence to provide a complete view of the attack chain

By strengthening correlation analysis capabilities, organisations can overcome the limitations of single-dimensional detection and achieve comprehensive identification of complex supply chain attacks. This particularly addresses the open-source software sustainability challenges mentioned in the study, reducing dependence on the security of individual components through better threat detection.

Phase 4: Is the Incident Response Process Consistently Effective?

In the SolarWinds incident response, although many organisations detected anomalies, the response process was slow and inconsistent, giving attackers sufficient time to achieve their goals. The issue lay in the lack of validated, consistent response processes and the continuous optimization of response efficacy.

Saixun Security Validation Method

In Phase 4, the core question the platform focuses on is: "Is our incident response process always consistently effective?"

In this phase, the platform can:

  • Validate end-to-end incident response workflows

  • Measure and optimise response timelines

  • Support incident tracing and root cause analysis

  • Utilise AI analysis to discover performance bottlenecks

  • Provide improvement recommendations based on actual data

By optimising response processes, organisations can ensure they take prompt and consistent action when supply chain attacks are discovered, thereby minimising losses. This directly addresses the challenge mentioned in the study of ensuring application partners report vulnerabilities, by establishing efficient vulnerability management and response mechanisms.

03 Ten Defence Measures from a Security Validation Perspective

Researchers identified 10 priority defence measures. We believe implementing these measures is only the first step; enterprises must establish validation mechanisms to ensure they are truly effective:

  1. Restrict Information Flow Across Trust Boundaries (Phase 1)

    1. Traditional Implementation: Set up network segmentation

    2. Validation Method: Perform network openness probing to continuously validate segmentation effectiveness

  2. Role-Based Access Control (Phase 1)

    1. Traditional Implementation: Set up a permission matrix

    2. Validation Method: Conduct regular privilege escalation testing to validate whether permission boundaries are truly insurmountable

  3. Monitor and Control Boundary Communications (Phase 1)

    1. Traditional Implementation: Configure firewall rules

    2. Validation Method: Conduct network penetration testing to validate the effectiveness of boundary controls

  4. Monitor Configuration Setting Changes (Phase 1)

    1. Traditional Implementation: Establish configuration baselines

    2. Validation Method: Attempt unauthorised configuration changes to validate whether detection and audit mechanisms are triggered

  5. Protect Information at Rest (Phase 2)

    1. Traditional Implementation: Implement encryption

    2. Validation Method: Conduct data exfiltration testing to validate whether sensitive data leakage is detected

  6. Continuous System Monitoring (Phase 2)

    1. Traditional Implementation: Deploy monitoring tools

    2. Validation Method: Test the detection capabilities of monitoring systems through simulated attacks to assess for detection blind spots

  7. Enable Authentication (Phase 2)

    1. Traditional Implementation: Implement multi-factor authentication

    2. Validation Method: Conduct social engineering testing and credential testing to assess the resilience of the authentication system

  8. Threat Modelling and Attack Surface Analysis (Phase 3)

    1. Traditional Implementation: Conduct threat modelling exercises

    2. Validation Method: Test hypothetical attack scenarios to validate whether all critical threat vectors have been identified

  9. Update Vulnerable Dependencies (Phase 4)

    1. Traditional Implementation: Deploy vulnerability scanning tools

    2. Validation Method: Trigger security validation based on vulnerability scanning results to provide a basis for remediation prioritisation

  10. Remediate Vulnerabilities Based on Risk (Phase 4)

    1. Traditional Implementation: Formulate vulnerability remediation priorities

    2. Validation Method: Conduct risk validation assessments to confirm whether priority categorisation truly reflects business needs

04 Comprehensive Supply Chain Security Validation Strategy

Based on the research findings and Saixun's four-phase security validation process, we suggest organisations adopt the following strategies to strengthen supply chain security:

  1. Establish a Validation-First Culture: Do not settle for framework compliance alone; ensure security products are truly effective through continuous validation.

  2. Formulate a Security Baseline Monitoring Mechanism: Establish an enterprise-specific security baseline through continuous observation and detection, and formulate monitoring mechanisms.

  3. Implement Real-World Assessments: Regularly test security products using real-world attack scenarios to understand defensive system performance in actual combat.

  4. Strengthen Correlation Analysis Capabilities: Move beyond single-dimensional detection to construct comprehensive threat identification capabilities.

  5. Optimise Response Processes: Continuously improve incident response processes based on actual data to ensure consistent and effective threat resolution.

  6. Leverage AI to Enhance End-to-End Performance: Integrate AI technology into various security phases to achieve automated and intelligent security validation.