You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When considering scanning for the target application, we should provide a simple and useful API to prevent users to know how our services communicate with each other. Ideally, we should hide the inter-service communication inside by introducing the Scan class.
You should make sure that the user is able to create multiple concurrent scans to speed up the flow and limit the attack surface. To hide implementation details and reduce complexities while creating an instance of Scan, you should implement a factory that will be in charge of creating scan with a particular configuration.
The ScanSettings interface should be generic and straightforward. For starters, it should include tests, a couple of parameters to optimize scanning, and info about the target application.
The crawler and other discovery methods can be easily used to set up a scan from scratch. However, in some cases, to improve the attack surface and define explicit boundaries it is better to build a HAR before starting a new scan. To address the complexity while creating HAR request, you can use the Builder or Factory pattern that helps you to hide details of how to deal with a particular kind of postData or cookies:
When considering scanning for the target application, we should provide a simple and useful API to prevent users to know how our services communicate with each other. Ideally, we should hide the inter-service communication inside by introducing the Scan class.
You should make sure that the user is able to create multiple concurrent scans to speed up the flow and limit the attack surface. To hide implementation details and reduce complexities while creating an instance of Scan, you should implement a factory that will be in charge of creating scan with a particular configuration.
The ScanSettings interface should be generic and straightforward. For starters, it should include tests, a couple of parameters to optimize scanning, and info about the target application.
The crawler and other discovery methods can be easily used to set up a scan from scratch. However, in some cases, to improve the attack surface and define explicit boundaries it is better to build a HAR before starting a new scan. To address the complexity while creating HAR request, you can use the Builder or Factory pattern that helps you to hide details of how to deal with a particular kind of postData or cookies:
The text was updated successfully, but these errors were encountered: