Integrations

integration information is found under the integrate menu option the overview tab provides information on where various scan types fit into the traditional sdlc additional tabs exist for each of the types of scans supported by soos (see getting started with soos docid 44xyviv7holkuojonqf9h for more information) the external connections tab contains all other integrations, such as jira docid\ cjyiue8qyifgmtuo gvto , slack integration docid 9pwjhzjuu eyn8 2mtnc2 , and more integration overview understanding scan integrations the layout and usage of each of the scan integration tabs are similar, the example below is for sca sca integration options ci/cd selection the left tab menu, contains a selection of ci/cd systems for which soos has already created some boilerplate helper code, as well as a generic script integration option which should work for any other system or to run locally api credentials the account drop down will always contain you (the user's) credentials, but there may also be one or more service accounts docid\ flgpbrdwonibtjlg5ncru listed selecting alternate accounts will change the api keys available we strongly recommend using a service account for any integration run in an automated fashion, such as a ci/cd system two api keys are available and can be regenerated at any time, use a key rotation scheme to ensure that no downtime is necessary when changing/regenerating keys the client id (in addition to an api key) is required for any script invocation be sure to store your client id and api key securely integration options for some systems there are multiple integration options, such as various file formats, in the example above there is only one listed use the provided links to browse the readme as well as the github link to the open source script that will be run when you integrate a sample snippet for each supported environment is also provided (use the environment drop down to change between linux/windows/mac)