82

You have identified only one risk, that of an attacker identifying machine roles on the network by using predictable host names. I think you missed the competing risk, that of increased operator error by not using predictable and descriptive host names. This is how I would assess those conflicting measures: Use unpredictable host names Benefit(s) An ...


51

Data destruction is a technique of last resort. If you are planning to use a new storage device, you should use full disk encryption. This allows you to either destroy the encrypted master key or simply forget the password, effectively rendering all data unrecoverable, despite no data actually being wiped. Encryption is a solution for both solid state and ...


32

Everybody's (me included) reflex answer to such a question will normally be: Huh huh huh (falls off chair). No! How would you think this could even work? Executables are signed nowadays, which prevents them from being modified! However, if you consider "exe" files in general, not just those from a fresh naked Windows install, the answer must be: Careful!. ...


23

This could be related to almost anything, personal information are sold just like any other "things" on the darkweb and even on the "web" by relatively legal entities, Databrokers are selling personal information just like any other stuff. In addition to this as @anon said OSINT tools might be used to gather information about persons, and there are lot of ...


20

The fact that there is no readily available information to support your conclusion, should give you some idea about its validity. The point is, that if your attacker is already in, he will need to do some additional foot-printing anyway. Your host name may be database.xyz.intranet, but if the nmap gives you 1521 (oracle), 1433 (sql server) or 5432(Postgress)...


18

Windows system executables do not contain any sensitive information. They may reveal the version of the operating system you are using, but personal information is not stored in executables. Instead, it is stored in configuration files or databases kept throughout the system. While it would be theoretically possible to store sensitive information in ...


15

What you're advocating for is called "security though obscurity". While in theory obscurity does provide some extra protection while not making things worse, it usually does make things worse in practice. It (1) adds complexity to the system which leads to errors, (2) dilutes the understanding of what information is secret and what isn't, and (3) may have a ...


13

Tl;dr: Because you can never trust all storage drives to securely wipe themselves, you must plan as if none of your drives can be securely wiped. Placing a dependency on the type of media is not the right way to approach the problem, because the technology is always evolving and changing, and you can never be in 100% control of all IT spend. Remember that ...


10

This kind of attack is called shoulder surfing and it is a real problem. Hardly a day goes by where I do not see someone putting themselves at risk of this either on the train, a cafe or in various other public places. There are a number of countermeasures, most of which are as simple and basic as the attack itself. Situational awareness Beware of your ...


9

When your organization is subject to the GDPR, then it should have a designated Data Protection Officer. This person is responsible for ensuring that data protection laws are applied within the organization. This should be the first place to report to.


8

One way to check for personal information is by using google. Just insert the string you want to search for and surround it with ". Like "NAME SURNAME". This will display some sites where exactly this match is found. You can check for other personal data from that mail, too. That way you propably can get close to the source of the information leakage. There ...


8

if you can contact the recipient by other means besides email, one easy way to send securely content over email is putting the content (images,documents,etc) into a encrypted container (a zip, 7zip, .rar file) that is protected with a secure and not easily guessable password. Then after you sent the email contact the recipient and provide them with the ...


8

If you encrypt the disk from the start, when you first start using it, then this isn't a problem. All data you write is encrypted and remapped sectors just lead to encrypted data being remanent on the over-provisioned area. Since the data is encrypted, you can't do anything with it even if you recover it using direct flash reads on a disassembled SSD. ...


8

They can contain file paths from the system they were compiled on, which may be sensitive if these are programs you compiled on your own system.


7

FDE does not need to know anything about overprovisioning. If the partition is encrypted, no plain-text will ever be written anywhere. Blocks reserved for wear leveling will either have un-initialized random data, or encrypted blocks. If you are using the encryption provided by the controller, encryption/decryption occurs inside the controller, so no plain ...


5

Your PI (personal information) is your PI, and in the 21st century you can't really avoid to spread it around everywhere. That means when someone has your PI it's hard to find out from where they might have gotten it. In some countries you have a legal right to ask companies to tell you, but that obviously only works if the source of the email is easily ...


5

it seems there is one prime contender for the solution, which is to encrypt parts of the URI or all of it. Hashing does not seem to be an option since the data is highly predictable and calculating the entire set of values is easy. Encrypting the entire URI will limit a lot of the advantages of the approach. Symmetric encryption requires ...


5

The answer is mentioned next to the sentence in the cheat sheet that you read. Do not use RDBMS database, row or table level encryption. The data can be retrieved in the clear by anyone with direct access to the server, or over the network using the application credentials. It might even traverse the network in the clear despite being "encrypted" on ...


5

In the blog post about the new feature, Signal says: Message contents are end-to-end encrypted with the Signal Protocol as normal, but the “envelope” containing the sender certificate as well as the message ciphertext is then also encrypted using the sender and recipient identity keys: The feature is designed to hide the sender of the message from plain ...


4

To simply put, there isn't any "one true secure method". Why, you might ask? Because computing has always been about trust, whether implicit or explicit. Regardless if it was the 1960's or today, you trust the machine in question to act like you expect. This can prove quite an issue, because potentially, you could be dealing with a software or hardware ...


4

I am thinking about encryption as well as using a proprietary format to make it difficult to reverse engineer anything..... I want to create a file format that will be difficult to reverse engineer so that application is safe. A file format which is difficult to reverse engineer is way more difficult to implement correctly in the application than a ...


4

Apple Touch ID has an FAR of 1/ 50,000 while Face ID has a FAR of 1 / 1,000,000 https://support.apple.com/en-us/HT208108 Android also insists on having an FAR of not higher than 0.002% (1 in 50,000). (Source: Android 7.0 Compatibility definition document) A company called Eyeverify has a very relevant blog on this topic. They too seem to suggest that an ...


4

Hiding who is sending the message is indeed the intent of the feature. In many cases it should be effective, but as they note in their blog post, there are still improvements to be done: These protocol changes are an incremental step, and we are continuing to work on improvements to Signal’s metadata resistance. In particular, additional resistance to ...


4

What you are seeing is a cached view of the previous partitions. If they appear to persist even after a wipe, this is a result of the kernel caching the last known partition table in memory. It does this because it does not expect the layout to change at runtime, so rather than re-read the table each time the partition layout is queried, it reads it once at ...


3

If you are worried that websites where you sign up are leaking your information, one possible way of tracing a leak is by signing up with slightly different names and email addresses to each website. The easiest way to do this is by changing your middle name. So you would sign up to one website as John A. Djuro, to the next one as John B. Djuro, then John C....


3

How to protect a PC against sensitive data access by malicious app/driver A driver, by definition, is part of the operating system. As such, whenever someone is able to place a malicious driver, it gets access at a system level of privileges. That means it can access every single bit of memory your computer has. You lost the game. The only way to ...


3

As long as you trust this institution, and that they are who they say they are, I would simply recommend encryption. Encrypt the e-mail if your e-mail application supports it, and the recipient supports it. If you can't encrypt the whole e-mail, you should at the very least be able to encrypt a zipped file of the image, and provide the password used to ...


3

Browser fingerprinting The issue you are describing is one technique out of many in the field of browser fingerprinting. There are three main types of browser fingerprinting, often related. In order of amount of research, they are: Device fingerprinting, which aims to distinguish individual users. It focuses on finding unique identifiers on a browser when ...


2

I was reminded of this because it came up as a "popular question." Since I asked this I have learned that the OWASP recommendation is to use request headers: In POST/PUT requests sensitive data should be transferred in the request body or request headers In GET requests sensitive data should be transferred in an HTTP Header While this makes the API ...


2

Does this approach seem valid and/or is there anything else I am missing? Your approach is valid, however; I wouldn't dismiss using a preshared symmetric key for the following reasons. Asymmetric is far slower to decrypt than symmetric. If the service has to decrypt multiple values from your URI performance could be impacted. The attack vector for this ...


Only top voted, non community-wiki answers of a minimum length are eligible