Performing data input checks

Technical unit-level testing doesn’t have to end at syntax and payload references. When we begin to utilize pipelines for deploying at scale to many different systems, we can also account for requirements such as the technical limitations of a vendor and perform additional coverage tests using different inputs for our test cases. Although this chapter has had input as part of the validation logic, we haven’t focused on the outcomes of use case coverage and impact.

In the upcoming labs, we’ll be focusing on leveraging the detections themselves as inputs for validating technical compliance requirements that may be specific to your environment and simulating coverage with test cases that we as engineers would have to develop or pull from other research.

Lab 5.3 – Palo Alto signature limitation tests

In this lab, we will examine compatible Snort-style signature detections that modern Palo Alto Next Generation Firewalls ...