Can HumDay connect to Google Security Scanner?

Yes. HumDay reads Google Security Scanner's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 11 operations are documented.

Do I need to write code to automate Google Security Scanner?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Security Scanner account.

What can HumDay do in Google Security Scanner?

5 of the 11 documented operations change something in Google Security Scanner, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Security Scanner account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Security Scanner is held behind that approval.

Automate Google Security Scanner

HumDay reads Google Security Scanner’s own published API description and derives 11 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Google Security Scanner is

Scans your Compute and App Engine apps for common web vulnerabilities.

API host: websecurityscanner.googleapis.com

What HumDay can do in Google Security Scanner

5 documented operations change something in Google Security Scanner.

POSTCreates a new ScanConfig./v1beta/{parent}/scanConfigs
DELETEDeletes an existing ScanConfig and its child resources./v1beta/{name}
PATCHUpdates a ScanConfig. This method support partial update of a ScanConfig./v1beta/{name}
POSTStops a ScanRun. The stopped ScanRun is returned./v1beta/{name}:stop
POSTStart a ScanRun according to the given ScanConfig./v1beta/{name}:start

What HumDay can read from Google Security Scanner

These are the operations a schedule or a trigger can watch.

GETList Findings under a given ScanRun./v1beta/{parent}/findings
GETLists ScanRuns under a given ScanConfig, in descending order of ScanRun stop time./v1beta/{parent}/scanRuns
GETList CrawledUrls under a given ScanRun./v1beta/{parent}/crawledUrls
GETList all FindingTypeStats under a given ScanRun./v1beta/{parent}/findingTypeStats
GETGets a Finding./v1beta/{name}
GETLists ScanConfigs under a given project./v1beta/{parent}/scanConfigs

How automating Google Security Scanner works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Google Security Scanner account.
Grant access, then go live. You approve the specific Google Security Scanner operations it may use — and only those.