Cleans up AI for Security section #564
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
natasha-moore-elastic
approved these changes
Feb 25, 2025
|
this PR got wrecked. Making changes in #737 |
benironside
added a commit
that referenced
this pull request
Mar 11, 2025
Second version of #564. Cleans up the AI for security section. Content has already been reviewed and approved.
thekofimensah
pushed a commit
that referenced
this pull request
Mar 21, 2025
Second version of #564. Cleans up the AI for security section. Content has already been reviewed and approved.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of the work tracked here, cleans up the AI for Security section: fixes links and images, removes migration artifacts and raw source files, fixes videos, etc.
Affected pages: every page in the AI for security section, except AI Assistant and AI Assistant knowledge base. So that means the section landing page, the Attack discovery page, the Set up LLM connectors pages, and the use cases pages are affected.