Vulcan Cyber

the vulcan cyber connector facilitates the retrieval and management of vulnerability data, enabling enhanced security automation within the swimlane ecosystem vulcan cyber is a vulnerability management platform that enables organizations to effectively prioritize and remediate vulnerabilities the vulcan cyber connector for swimlane turbine allows users to retrieve detailed vulnerability data, apply custom search criteria, and streamline vulnerability management processes by integrating with vulcan cyber, swimlane turbine users can enhance their security posture with targeted vulnerability insights and automated remediation workflows, ensuring that critical risks are addressed promptly and efficiently prerequisites to integrate vulcan cyber with the swimlane turbine platform, ensure you have the following http bearer token authentication with these parameters url endpoint for vulcan cyber api access token a valid bearer token to authenticate api requests capabilities the vulcan cyber connector has the following capabilities retrieve vulnerabilities api documentation https //help vulcancyber com/en/articles/3438656 working with vulcan api configurations vulcan cyber api token authentication authenticates using bearer token configuration parameters parameter description type required url a url to the target host string required token the api key, token, etc string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional actions retrieve vulnerabilities retrieve a list of vulnerabilities from vulcan cyber using specified search criteria and return the results endpoint url /api/v2/vulnerabilities method post input argument name type required description ruleset object optional the set of rules to filter the search results ruleset operator string optional the operator that applies to the rules within the ruleset this operator will be applied to all sub rules ruleset rules array optional the list of all rules to apply on the returned output ruleset rules category name string optional the category name for the parameter ruleset rules parameter name string optional the parameter name or column name to which the rule applies ruleset rules parent name string optional the parent category name, if applicable ruleset rules operator string optional the operator for the condition ruleset rules value string optional the value of the condition version number optional the version to use page number number optional the current page number in pagination default 1 page size number optional the number of results per page in pagination maximum 10000, minimum 1 order by array optional the column to order the results by order by parameter name string optional the name of the parameter to order by order by order string optional the order type, either ascending (asc) or descending (desc) columns array optional the specific columns to include in the search results input example {"json body" {"ruleset" {"operator" "and","rules" \[{"category name" "vulnerability","parameter name" "category","operator" "in","value" "vulnerable"}]},"version" 1,"page number" 1,"page size" 100,"columns" \["id","max risk","vulnerability name"]}} output parameter type description data array response data data id number response data data max risk number response data data vulnerability name string response data pagination object output field pagination pagination page number output field pagination page pagination limit number output field pagination limit pagination total pages number output field pagination total pages pagination total items number output field pagination total items status object status value status code number status value status message string status value status details object status value status timestamp string status value output example {"data" \[{"id" 1,"max risk" 9 8,"vulnerability name" "vulnerability a"},{"id" 2,"max risk" 9 5,"vulnerability name" "vulnerability b"}],"pagination" {"page" 1,"limit" 100,"total pages" 10,"total items" 1000},"status" {"code" 200,"message" "success","details"\ null,"timestamp" "2024 05 23t14 52 00z"}} response headers header description example content type the media type of the resource application/json date the date and time at which the message was originated thu, 01 jan 2024 00 00 00 gmt