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

Reported button #1226

Open
securitygeneration opened this issue Oct 8, 2018 · 12 comments
Open

Reported button #1226

securitygeneration opened this issue Oct 8, 2018 · 12 comments

Comments

@securitygeneration
Copy link

It would be nice to add a button that marks a particular user as having reported an email as phishing. While I know the current functionality is designed to be integrated into other reporting tools, the majority of 'reports' are still by email to the IT or security team, and it would be nice to be able to log that within GoPhish for metrics purposes.

@dsmurf
Copy link

dsmurf commented Oct 9, 2018

Where do you want the report button to be?
you can program it in html.

@securitygeneration
Copy link
Author

I envisage it should live at the bottom of the user detail timeline. And when you click it, a Reported entry get entered into the timeline, and the button disappears (no point in multiple reports).

image

@dsmurf
Copy link

dsmurf commented Oct 10, 2018

Ahhh you want a button in the admin panel where a admin can mark that a user reported the mail.
that might be out of my scope.

@securitygeneration
Copy link
Author

Yeah. I think this should be fairly trivial to implement.

@jordan-wright
Copy link
Collaborator

I like the idea in your screenshot, @securitygeneration. I think this is a good place to put a general "Actions" section that can be populated with various actions, as needed.

For example, in addition to marking the user as reported, I'd like to also offer a button that can re-send the email in the case of errors.

The thing is- I don't want to just have this point to the /report endpoint, since that might be misleading. For example, we collect the user-agent and IP address of the person who hit that endpoint so that might cause the logs to appear mismatched. Instead, I'm considering establishing API endpoints at campaigns/<id>/results/<rid>/report, campaigns/<id>/results/<rid>/resend, etc. We can then find a way in the logs and UI to indicate that an admin manually performed that action on behalf of the user.

Curious to hear y'all's thoughts!

@dsmurf
Copy link

dsmurf commented Oct 16, 2018

Jordan i think this would be awesome,.Would love that.

@securitygeneration
Copy link
Author

Resending would indeed be nice to have.

I agree that you'd want to be able to track an email as 'reported' without logging the rest of the info normally captured from the reporting user (IP, user agent, etc).

@mcvic1rj
Copy link

@jordan-wright a suggestion for the new report endpoint is to allow it to take a datetime object as well. That way you can insert the event, and have it displayed in the correct location in the timeline.

@dsmurf
Copy link

dsmurf commented Oct 29, 2018

Is there any timeline on this?

@FLX-0x00
Copy link
Contributor

FLX-0x00 commented Mar 4, 2020

I would love to see the "report" -button in the admin interface. Most customers receive individual phone calls and have to copy the RID from the admin interface and send it to the /report api. A good implementation could be to make the icon <i class="fa fa-times-circle text-center text-muted"></i> clickable in ordner to mark the email as reported directly. I will give it shot and try to implement this on my own. Should be not too hard.

@FLX-0x00
Copy link
Contributor

FLX-0x00 commented Mar 4, 2020

commited to my fork, works like a charm. feedback welcome

evait-security@91fd9d1

@FLX-0x00
Copy link
Contributor

@jordan-wright since the functionality is added into master the issue can be closed i think =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants