Skip to content

Instantly share code, notes, and snippets.

@joshuaaguilar20

joshuaaguilar20/readme.md

Last active August 31, 2020 21:09
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save joshuaaguilar20/dc0a71cc8521cd0d50fa5af0f8393915 to your computer and use it in GitHub Desktop.
Save joshuaaguilar20/dc0a71cc8521cd0d50fa5af0f8393915 to your computer and use it in GitHub Desktop.
Download ZIP
Speech notes
Raw
readme.md

The Problem:

  1. Simply Blocking Urls is not enough to train users to relate submissions to urls.
  2. 2021 25 % of all phishing breaches will occur from a mobile device broswer. -reference owasp-top 10
  3. Can we create eyes and ears for the client on minimal premissions and processing power ?

The objective was to use peoplecentric methods to help train users on what urls they are submitting to. The idea was inspired by the https lock so many users are familre with. I then started to wonder if there was a way to do this with input DOM data. if a client asked us if a url was a phishing scam or not, how do we know?

-- where is the data going -- what url is the user providing data to.

can we do this for our clients when they vist a login? By leveraging colors, a neurologic trigger to subconsciously train users into looking at where information is being sent. This helps provide postive feedback to users and data to proofpoint. The tool was designed to work in the broswer as it can work on mobile or laptop devices. mobile devices can often end up concealing signs indicative of potential phishing attacks and other cybersecurity threats. That said, security experts predict that in 2021, 25 percent of all data breaches will involve off-premises assets and mobile devices.

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