Hot answers tagged

35

The SHA-3 hash competition was an open process by which the NIST defined a new standard hash function (standard for US federal usages, but things are such that this will probably become a worldwide de facto standard). The process was initiated in 2007. At that time, a number of weaknesses and attacks had been found on the predecessors of the SHA-2 functions ...


30

Keccak was selected by NIST on October 2, 2012 as the winner of the contest. It is widely seen as a suitable alternative to SHA-2, because the design is so different from most previous hash standards that even if SHA-2 is broken, confidence in Keccak should be relatively unaffected. It is also very fast and simple to implement in hardware. NIST and most ...


17

"Best" is rather subjective - it depends on your requirements. That said, I'll give you a general overview of each mode. ECB - Electronic Code Book. This mode is the simplest, and transforms each block separately. It just needs a key and some data, with no added extras. Unfortunately it sucks - for a start, identical plaintext blocks get encrypted into ...


8

There is nothing more secure than "secure". An attacker who can break it upfront, because it has "only" 128-bit security, is an attacker who has way more available computing power than all computers on Earth taken together (even including smartphones and coffee machines). It is implausible that such an attacker would swoop down so low as to bother breaking ...


7

There's at least one usage for which SHA-2 is seemingly better than SHA-3 and that's key stretching. SHA-3 was designed to be very efficient in hardware but is relatively slow in software. SHA-3 takes about double the time compared to SHA-2 to run in software and about a quarter of the time to run in hardware. Since SHA-3 takes double the time to run in ...


7

NIST publishes a lot of test vectors. Including for HMAC (near the end of that page). In the file contained in the Zip archive, the vectors for HMAC/SHA-256 ought to be the ones with the parameter "L=32".


6

It took nearly a year, but NIST has released this bulletin explaining the update and also providing the updated document for SP 800-52 Revision 1. The answer to your question is expressed in the bulletin: NIST published the original version of SP 800-52 in 2005, but withdrew it in March 2013 because the guideline had not yet been updated based on ...


6

Updated: see Ryan Fisher's answer to this question, SP800-52 revision 1 was later released, and it's double the size of the original 2005 version. It was withdrawn because it lacked information on contemporary TLS versions and known security issues (i.e to prevent misinforming, until it could be updated). It was not "retired" (or "expired"), it was ...


6

On the 2nd of October, 2012, NIST decided what algorithm was going to be used to perform hashing. This was the Keccak algorithm. The Keccak algorithm is based on the hermetic sponge strategy. It's the new standard algorithm. We use standards to make have better compatibility. Keccak was designed by Guido Bertoni, Joan Daemen (one of the creators of AES), ...


5

This certification is typically done through FIPS certification. The list of labs certified by NIST to perform FIPS certifications is here


4

Believe the only way is to write your own custom password filter. There are also plenty of third party products that will do this for you e.g. http://nfrontsecurity.com/products/nfront-password-filter/ http://www.anixis.com/products/ppe/default.htm Even Windows 2008 password complexity will only check: Passwords cannot contain the user’s account name ...


4

I haven't tested OpenSSL but I'm pretty sure it implements AES-CBC correctly. Your program, however, obviously uses different data, so it isn't surprising that you get different results. The test vectors are given out in hexadecimal. For example KEY = 0000000000000000000000000000000000000000000000000000000000000000 IV = 00000000000000000000000000000000 ...


4

In general, DISA STIGs are more stringent than CIS Benchmarks. Keep in mind that with STIGs, what exact configurations are required depends on the classification of the system based on Mission Assurance Catagory (I-III) and Confidentiality Level (Public-Classified), giving you 9 different possible combinations of config requirements. CIS usually have a Level ...


3

Here are some important considerations: What is the reason that you're hardening against a given benchmark or guideline? Are you going to be audited? Is there a preferred route or route the your auditors are more familiar with? What tools will you use for self auditing? Do those tools have polices or plugins to audit your system against a given ...


3

I'm unsure whether this is the policy you're looking for, but perhaps it just slipped your attention. On the server side (this is Windows 2003) you have this: It allows you to define the settings for the RDP sessions over network. Otherwise it's possible this is what you are looking for. I left a comment on your question, perhaps you can clarify there if ...


3

It seems to me that there are three major options: Add TLS on top of Winsock using SChannel; Enable IPsec using WSASetSocketSecurity - you probably need to understand quite a bit about IPsec before using this option; Tunnel your connection to the server using any kind of protocol (SSH and TLS are probably the ones most used). What you don't want to do is ...


3

One benefit I see of SHA-3 over SHA-1 and SHA-2 is that it is not sensitive to extension attacks. That means that protocols based on it (e.g. MACs) are inherently more robust.


2

ISO/IEC 27002:2015 Section 9) Access Controls Subsection 9.4.2 - Secure logon procedures "Implementing and using suitable authentication techniques, not disclosing sensitive information at log-on time, data entry validation, protection against brute-force attacks, logging, not transmitting passwords in clear over the network, session inactivity timeouts, ...


2

Every FIPS 140-2 device must have a publicly available non-proprietary Security Policy document which is obtainable from the FIPS 140 program web site (CMVP - http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm). Although some Security Policies are far better written than others, there is a minimum requirement for these documents that should ...


2

Your Information Security Policy is different from your Information Security Plan: Your Information Security Plan should include all required actions for organization-wide implementation of your Information Security Policy. Although the two are closely tied, they are also separate documents. A solid Information Security Plan will typically include ...


2

One difference is the ease to find a reliable and automated tool to check for compliance. I believe Nessus has templates available for most of the ones you have listed, but some are dated. In any case, I'd choose one that makes it as easy as possible for you to check and stay in compliance.


1

I realize this post does not directly answer your question, but I thought I'd post it anyway as a "devil's advocate" rebuttal to Thomas's post. I fully agree with Thomas; there is no one who could give any reason to think you'll ever need more than 128 bits of security in our lifetime. That being said, Bernstein, the author of Curve25519, did co-author ...


1

This FAQ about assigning vulnerability types implies that <vuln:security-protection> indicates that a vulnerability can be leveraged to gain access to a system. Access is the holy grail when trying to compromise a system since if you have access you can then compromise the system in any other way you want (availability, integrity, confidentiality). ...


1

cpe-lang shows if are other dependencies for the vulnerable product. If you look over the NVD CVE's you will see some products are vulnerable only on some specific platforms. For example <cpe-lang:logical-test negate="false" operator="AND"> <cpe-lang:logical-test negate="false" operator="OR"> <cpe-lang:fact-ref ...


1

The client proceeds as follows (I am considering only the encryption and signature steps as these are relevant for you): 1) Encryption: It generates a fresh 3DES symmetric key It encrypts the newly generated symmetric key with the public key of the server (using the RSA-PKCS1 algorithm, see EncryptionMethod algorithm) and places it into the ...


1

It's pretty easy to do with PAM, so that covers Linux/Solaris/FreeBSD at least. Among other things the pam_cracklib module offers that functionality. Its default setting is actually to check for five character changed but can be configured by the difok option.


1

The approach I would recommend for enterprises would be to integrate these systems with your directory service, which for most will be Active Directory. This way your password policy is set in a single place and it bring other benefits in managing access control and roles in a single place. You can also then provide single sign-on and two factor ...


1

I think this may have changed in Windows 2008 but in earlier versions of windows this kind of thing was done via custom password filters (passfilt.dll) and/or custom login agents.


1

Before answering your question, I would like to define a word you used (hardening). According to the all-knowing wiki, I will define it as "the process of securing a system by reducing its surface of vulnerability." To know which approach is right for you, you have to know what you hope to achieve. Some in the DoD (and other industries) may only apply STIGs ...



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