Assisting a scanning session

1. A method, executable by a networking device comprising a physical processor implementing machine readable instructions, the method comprising:

detecting, using the physical processor, a specific application programming interface (API) call from an application running on a production server to interact with the application;

determining, using the physical processor, whether the detected specific API call requires assisted scanning, wherein an occurrence of a first detected specific API call triggers assisted scanning and an occurrence of a second detected specific API call does not trigger assisted scanning;

responsive to the detected specific API call being an occurrence of the first detected specific API call, assisting, using the physical processor, a scanning session of the application based on the detecting of the specific API call; and

identifying, using the physical processor, a modification to the application based on the scanning session.

2. The method of claim 1 comprising:

receiving, using the physical processor, an authorization of the scanning session prior to detecting the API call.

3. The method of claim 1 wherein the first detected specific API call includes a file modification API, and wherein assisting the scanning session of the application based on the file modification API comprises:

skipping, using the physical processor, execution of the file modification API; and

reporting, using the physical processor, the skipped execution of the file modification API to a scanner.

4. The method of claim 1 wherein the first detected specific API call includes a file modification API, and wherein assisting the scanning session of the application based on the file modification API comprises:

backing, using the physical processor, up a file affected by the file modification API;

executing, using the physical processor, the file modification API; and

reverting, using the physical processor, the file affected by the file modification API to a state prior to execution of the file modification API.

5. The method of claim 1 wherein the first detected specific API call includes a database connection API, and wherein assisting the scanning session of the application based on the database connection API comprises:

directing, using the physical processor, the database connection API to a testing database, the testing database is a redundant database for execution of the database connection API.

6. The method of claim 1 wherein the first detected specific API call includes a database connection API, and wherein assisting the scanning session of the application based on the database connection API comprises:

executing, using the physical processor, the database connection API;

modifying, using the physical processor, a database based on the execution of the database connection API; and

reverting, using the physical processor, the database to a state prior to the modification of the database.

7. The method of claim 1 wherein the first detected specific API call includes an email related API, and wherein assisting the scanning session of the application based on the email related API comprises:

directing the email related API to a different email address.

8. The method of claim 1 wherein detecting the specific API call to interact with the application running on the production server comprises:

monitoring various API calls for the detecting of the specific API call.

9. The method of claim 1 wherein the detected specific API call includes at least one of a file modification API and a database connection API.

10. The method of claim 1 wherein an action associated with the assisting is determined based on a type of the detected specific API call, and wherein the action comprises at least one of: receiving an authorization of the scanning session, skipping an execution of an API, backing up a filed affected by an API, directing an API, reverting a database, and directing an API to a different email address.

11. The method of claim 1 wherein at least two actions associated with the assisting are determined based on a type of the detected specific API call.

12. A system to detect a specific application programming interface (API) call for providing assistance to a scanning session, the system comprising:

a scanner to:

perform the scanning session of an application;

a production server running the application, the production server comprising:

a security agent to:

detect a specific application programming interface (API) call from the scanner;

determine a type of the detected specific API call, wherein first and second types of detected specific API calls require performance of different first and second sets of operations, respectively;

based on the determination that the detected specific API call is the first type of detected specific API, provide assistance to the scanning session of the application in accordance with a first set of operations; and

detect a modification to the application based on the scanning session.

13. The system of claim 12 further comprising:

a redundant resource, communicatively coupled to the production server, to execute the detected specific API call.

14. The system of claim 12 wherein the security agent is to:

authorize the scanning session; and

monitor various API calls for the detection of the specific API call.

15. The system of claim 12 wherein the type of detected specific API call corresponds to a functionality of the application, wherein the first and second sets of operations comprise different ones of: receiving an authorization of the scanning session, skipping an execution of an API, backing up a file affected by an API, directing an API, reverting a database, and directing an API to a different email address.

16. The system of claim 12 , wherein the first detected specific API call includes a file modification API and wherein the production server:

skips execution of the file modification API; and

reports the skipped file modification API to the scanner.

17. The system of claim 12 , wherein the first detected specific API call includes a file modification API and wherein the production server:

backs up a file affected by the file modification API;

executes the file modification API; and

reverts the file affected by the file modification API to a state prior to execution of the file modification API.

18. The system of claim 12 , wherein the first detected specific API call includes a database connection API, and wherein the production server:

directs the database connection API to a testing database, the testing database is a redundant database for execution of the database connection API.

19. The system of claim 12 , wherein the first detected specific API call includes a database connection API, and wherein the production server:

executes the database connection API;

modifies a database based on the execution of the database connection API; and

reverts the database to a state prior to the modification of the database.

20. A non-transitory machine-readable storage medium comprising instructions that when executed by a physical processing resource cause a computing device to:

monitor various application programming interface (API) calls to interact with an application for detection of a specific API call;

based on the detection of the specific API call, assist with a scanning session related to the detected specific API call;

detect a modification to the application;

skip execution of the API call; and

report the skipped execution of the API call to a scanner.