Skip to main content

Terms of Use

By using, reading, browsing, skimming, linking, or referencing this site, you agree to the following:

Liability

The site and/or its staff and owners can not be held liable for the information on the site. The nature of the information posted requires assessment whether it is the suitable measure or information to use with regards to the subject matter.

Popular Posts

What is HTTPS, Encryption, and Cipher?

By now you may have heard that a secure website starts with HTTPS and not just HTTP. And you have been making sure the site is secure when you access certain resources or post sensitive data. That is well and good but there seems to be a misconception that secure automatically means legitimate or authenticate site. It is not. Just because a website uses HTTPS doesn't automatically make it the authentic and legitimate site. So what is the difference? To understand the difference let us first make sure HTTPS is understood in its basic meaning.

Attack Example - ClickJacking+Spoofing - UI Redress - Trusted User Interface

ClickJacking and Spoofing Attack Example - Trusted User Interface attack. It used to be that the most common operating system and browser being targeted for this kind of attack is Windows and IE. The underlying reason was that Windows has more users and Internet Explorer was basically File Explorer having a different user interface. Today, the attack surface is wider and much more complicated to notice. The screenshot posted here is a combination of a User Interface (UI) spoofing from a ClickJack.