#Security by obscurity example software
#Security by obscurity example code
#Security by obscurity example password

Is this a bad practice for cybersecurity? After reading our examples, you may have the answer.

In the case of web servers, the Nginx or Apache version can be hidden, which can keep attackers from knowing if you're running a vulnerable and outdated version.

#Security by obscurity example software

Hiding software versions: While there are a lot of ways you can perform a banner grabbing attack, one of the most popular STO techniques is to hide your software version from the public.

#Security by obscurity example password

A proper solution would be to disable password authentication, and limit logins by IP with mechanisms such as TCP Wrappers or a firewall. This technique works however, once a dedicated attacker finds your SSH port is running on a different port than 22, he'll start targeting your new port anyway. Using a different daemon port is a very popular technique for reducing the amount of brute force attacks against certain ports, such as port 22 on SSH.Changing the name of your application folder, for example from 'admin' to '_admin.' It may take longer, but if the attacker finds you are using '_admin', and there is no additional authentication or IP-based whitelist, he'll be able to jump right into your administrative area.This is a very popular technique that assumes the attacker won't read the code, and therefore, provides protection from any intrusion.

#Security by obscurity example code

Hiding user passwords inside binary code, or mixed with script code or comments.

In the cybersecurity world, there are other real-life scenarios where security by obscurity is seen every day: However, as soon as someone walks in and discovers your house, it's vulnerable. Being surrounded by trees and shrubs, it's 'secure' within that forest. The same goes for building your house in the middle of the forest. That's when your house becomes vulnerable. The principle is simple: your house will be 'secure' until a thief discovers the key in its hiding place. Hiding the key to your front door under a nearby rock or the welcome mat. And the first example that comes to mind is this one: To explain how security by obscurity works, we need to look at real-life examples.

By using security by obscurity, some people think they are going to minimize the risk of getting targeted by an attack. STO is based primarily on hiding important information and enforcing secrecy as the main security technique. Known also as 'STO,' 'security by obscurity' or simply as 'secrecy,' it's one of the ways systems engineers and software developers secure a system or an app. ¶What is security through obscurity? (STO)

How much critical data is really hidden in your online infrastructure?.

Is security through obscurity a bad thing?.

What is security through obscurity? (STO).

We know this topic opens a lot of discussions within the infosec community, and that's exactly why we're writing about it-to answer questions and demystify the doubts that constantly surround this topic. One thing that isn't always mandatory is applying security through obscurity. When you work as a system administrator, one of your main tasks is to keep your systems secure, and that includes applying system package updates, kernel patching, disabling unnecessary services, installing IDs and firewalls, and many other things.