-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ti_custom: Add docs about retrieving ISAC feeds #12098
base: main
Are you sure you want to change the base?
Conversation
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
Quality Gate passedIssues Measures |
- Authentication Credentials: Username, password, API Key, or client certificate, as required by the ISAC. | ||
|
||
3. Set up the integration: | ||
- The server URL and collection name should be used to build the URL as follows: `https://{server_url}/{api-root}/collections/{name}/objects/` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The server URL and collection name should be used to build the URL as follows: `https://{server_url}/{api-root}/collections/{name}/objects/` | |
- The server URL and collection name should be used to build the URL as follows: `https://{base_url}/{api-root}/collections/{name}/objects/` |
Matches what's in the url
variable description in the manifest, and avoids confusion with the above "Server URL" example https://example-isac.org/taxii/
, which I assume would be {base_url}
of example-isac.org
and {api-root}
of taxii
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor suggestion.
Proposed commit message
See title.
Checklist
changelog.yml
file.Related issues
Screenshots