Skip to content

docs(usage): improve OpenCTI connector setup steps (#6503) - #8014

Open
Abdullah (AzazelSensei) wants to merge 1 commit into
OpenAEV-Platform:mainfrom
AzazelSensei:docs-xtm-connector-6503
Open

Abdullah (AzazelSensei) wants to merge 1 commit into
OpenAEV-Platform:mainfrom
AzazelSensei:docs-xtm-connector-6503

Conversation

@AzazelSensei

Copy link
Copy Markdown
Contributor

Proposed changes

  • Name OpenCTI > Data > Ingestion > Monitoring view as the place to confirm the OpenAEV Coverage connector
  • Point the trigger steps at the OpenCTI Security Coverage docs

Testing Instructions

  1. Open docs/docs/usage/evaluate/xtm-suite-connector.md
  2. Confirm Step 3 names Data > Ingestion > Monitoring view
  3. Confirm the trigger section links to https://docs.opencti.io/latest/usage/security-coverage/

Related issues

Checklist

  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I wrote test cases for the relevant uses case
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality
  • For bug fix -> I implemented a test that covers the bug

…6503)

Name the OpenCTI Data > Ingestion > Monitoring view for checking the
OpenAEV Coverage connector, and point trigger steps at the OpenCTI
security-coverage docs.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

Documentation changes are clear with no unresolved review issues.

Pull request overview

Improves OpenCTI connector setup documentation with clearer verification and triggering instructions.

Changes:

  • Identifies the OpenCTI Monitoring view for verification.
  • Links to OpenCTI Security Coverage documentation.
File summaries
File Summary
docs/docs/usage/evaluate/xtm-suite-connector.md Clarifies connector verification and trigger instructions.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community Contribution from the community.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: improve the readability of how to set up OpenAEV as a connector with OpenCTI

3 participants