Repository navigation
Conversation
Disclosure: I am the CEO of Next Sight, the company behind Nexus. The guide is free and needs no registration.
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
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.
Disclosure: I am the CEO of Next Sight, the company behind Nexus.
Adds the Nexus OSINT Guide (https://www.nexus-osint.ai/osint) to Training, after Forensic OSINT KB Guides.
Why it fits the framework's free-resource rule: the guide is a free, public page with no registration or paywall. It is a long-form introduction to open source intelligence covering the intelligence cycle, core sources and techniques, evidence standards (including chain of custody), OPSEC, and the legal and ethical framework. A companion OSINT glossary is linked from the guide (https://www.nexus-osint.ai/glossary).
Entry: uses the enriched format from the README (pricing: free, registration: false, opsec: passive). I checked that arf.json still parses as valid JSON after the change.