Skip to content
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

Demonstrate how to integrate MDTI API notebooks with MISP playbooks #44

Open
cudeso opened this issue Aug 6, 2023 · 1 comment
Open
Assignees
Labels
enhancement New feature or request playbook:activity=6 Playbooks for activity 6

Comments

@cudeso
Copy link
Collaborator

cudeso commented Aug 6, 2023

See for examples of notebooks https://github.com/Azure/MDTI-Solutions/tree/master/Notebooks

Integrations:

  • Threat profiles
  • Vulnerabilities
  • Reputation scores
@cudeso cudeso added the enhancement New feature or request label Aug 6, 2023
@cudeso cudeso added the playbook:activity=4 Playbooks for activity 4 label Dec 7, 2023
@cudeso cudeso self-assigned this Dec 8, 2023
@cudeso
Copy link
Collaborator Author

cudeso commented Jun 17, 2024

Unable to test access with existing Azure account. Although docs state that a free account (which is also used for the sync with MSentinel/MISP) should work, access to "defender.microsoft.com" always returns "Selected user account does not exist in tenant 'Microsoft Services' and cannot access the application '80ccca67-54bd-44ab-8625-4b79c4dc7775' in that tenant. The account needs to be added as an external user in the tenant first. Please use a different account.".

@cudeso cudeso added the wontfix This will not be worked on label Jun 17, 2024
@cudeso cudeso closed this as completed Jun 17, 2024
@cudeso cudeso added playbook:activity=6 Playbooks for activity 6 and removed wontfix This will not be worked on playbook:activity=4 Playbooks for activity 4 labels Jul 16, 2024
@cudeso cudeso reopened this Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request playbook:activity=6 Playbooks for activity 6
Projects
None yet
Development

No branches or pull requests

1 participant