Skip to content

Conversation

@amee-sumo
Copy link
Collaborator

@amee-sumo amee-sumo commented Dec 5, 2024

Purpose of this pull request

This pull request is to create a new doc for Intel 471 Threat Intel

Select the type of change

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

DOCS-583

@amee-sumo amee-sumo added doc:new New section or topic to content do-not-merge Pull requests that should not be merged labels Dec 5, 2024
@amee-sumo amee-sumo self-assigned this Dec 5, 2024
@cla-bot cla-bot bot added the cla-signed Contributor approved, listed in .clabot file label Dec 5, 2024
@jpipkin1 jpipkin1 requested a review from a team as a code owner December 5, 2024 22:49
Copy link
Collaborator

@jpipkin1 jpipkin1 left a 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").

amee-sumo and others added 3 commits December 6, 2024 10:15
…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>
amee-sumo and others added 12 commits December 6, 2024 16:09
…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
amee-sumo and others added 3 commits December 9, 2024 12:40
…amework/intel-471-threat-intel-source.md

Co-authored-by: Jagadisha V <129049263+JV0812@users.noreply.github.com>
Copy link
Collaborator

@JV0812 JV0812 left a comment

Choose a reason for hiding this comment

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

LGTM

@yleiferman
Copy link
Contributor

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.

@jpipkin1
Copy link
Collaborator

jpipkin1 commented Dec 18, 2024

@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.

@jpipkin1
Copy link
Collaborator

jpipkin1 commented Dec 18, 2024

@yleiferman yleiferman enabled auto-merge December 18, 2024 17:55
@yleiferman yleiferman added this pull request to the merge queue Dec 18, 2024
Merged via the queue into main with commit bfd1461 Dec 18, 2024
7 checks passed
@yleiferman yleiferman deleted the Intel471-Threat-Intel-C2C branch December 18, 2024 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file do-not-merge Pull requests that should not be merged doc:new New section or topic to content

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants