-
Notifications
You must be signed in to change notification settings - Fork 228
Intel471 threat intel c2 c #4845
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
Conversation
…gic/sumologic-documentation into Intel471-Threat-Intel-C2C
docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/index.md
Outdated
Show resolved
Hide resolved
...data/hosted-collectors/cloud-to-cloud-integration-framework/intel-471-threat-intel-source.md
Outdated
Show resolved
Hide resolved
jpipkin1
left a comment
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.
Looks great, @amee-sumo! I have only a few suggestions. Also, I changed the CID from 10126 to 10127 to fix a merge conflict, and I added the new source to the product list (see commit "Add to product list").
…amework/index.md Co-authored-by: John Pipkin (Sumo Logic) <jpipkin@sumologic.com>
…amework/intel-471-threat-intel-source.md Co-authored-by: John Pipkin (Sumo Logic) <jpipkin@sumologic.com>
docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/index.md
Outdated
Show resolved
Hide resolved
…amework/intel-471-threat-intel-source.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
…amework/intel-471-threat-intel-source.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
…amework/intel-471-threat-intel-source.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
…amework/intel-471-threat-intel-source.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
…amework/intel-471-threat-intel-source.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
…amework/index.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
…amework/index.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
Changed "Intel 471" to "Intel471" based on the naming convention in our Sumo platform
...data/hosted-collectors/cloud-to-cloud-integration-framework/intel-471-threat-intel-source.md
Outdated
Show resolved
Hide resolved
…amework/intel-471-threat-intel-source.md Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
…gic/sumologic-documentation into Intel471-Threat-Intel-C2C
...data/hosted-collectors/cloud-to-cloud-integration-framework/intel-471-threat-intel-source.md
Outdated
Show resolved
Hide resolved
…amework/intel-471-threat-intel-source.md
JV0812
left a comment
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.
LGTM
|
Hi @amee-sumo and @JV0812 , thank you for creating this documentation. As of now, the threat intelligence functionality is in beta, so can you update the docs to not make it official yet? Please let me know if you have any questions. Maybe @jpipkin1 can you help during our timezone? My plan is to enable it for beta customers today. |
|
@yleiferman, if this is beta functionality, the Intel471 Threat Intel Source article should be marked as beta as shown in our style guide, like the STIX/TAXII 1 Client Source and the STIX/TAXII 2 Client Source articles. I can update this PR to do that. |
|
@yleiferman, the article is now marked as beta, and will be published here: |
Purpose of this pull request
This pull request is to create a new doc for Intel 471 Threat Intel
Select the type of change
Ticket (if applicable)
DOCS-583