-
Notifications
You must be signed in to change notification settings - Fork 87
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
[Feature]: Add Title/Description Field into LookyLoo #971
Comments
Thank you for the detailed feature request, I'll work on it over time, probably starting from the categorization, which is already there but only accessible to the admins. The first step will probably be to expose the categorization to all, and manually validate them after the fact (we cannot expect people to categorize the captures properly on the public instance). This capture category can then be attached to the MISP event as a tag. The title/description part is a bit more tricky as it is free text, and much more prone to issues/typos. This one will probably not be exposed to the non-admins any time soon. Then, I'm not sure what you mean by |
Alright, makes sense, especially when you submit a bunch of URLs, having them pre-tagged would be good. |
@danieleperera: Quick update on that: it is now possible to categorize captures using (for now) one MISP Taxonomy, and it is only doable after the capture is done and from the UI. But that was a required step for your request. I want to avoid the free text option as long as possible because it's going to make sharing the categories/tags a complete nightmare. We probably need to come up with a better taxonomy than the one we're using right now ( |
Feature Request: Add Title/Description Field into LookyLoo
It would be beneficial to add a new field, such as "Title" or "Description," in the database to enhance the tracking and organization of URLs being analyzed. This would provide better context for the URLs and can be quickly used to find a case.
Describe the solution you'd like
Proposed Solution
Benefits
Describe alternatives you've considered
No response
Additional context
This addition would streamline workflow and provide a clearer, more organized overview of analyzed URLs.
The text was updated successfully, but these errors were encountered: