Skip to main content

RAID

RAID


  • Stands for Redundant Array of Inexpensive Disks (or Redundant array of Independent Disks)
  • It is a data storage virtualization technology that combines multiple physical disk drives into logical units to ensure data redundancy and performance improvement
  • The standard RAID levels including there features and the number of disks that ensure their functionality are :
RAID levelsFeaturesNumber of disks
RAID 0StripingAt least 2
RAID 1MirroringAt least 2
RAID 5Striping with parityAt least 3 but upto 16
RAID 6Striping with double parityAt least 4
RAID 10Combining mirroring and stripingAt least 4
RAID types

A bit more...


RAID 0 : It improves the disk subsystem performance, but it does not provide fault tolerance

RAID 1: It uses same disks which both hold the same data. If one disk fails, the other disk continues to operate as usual.

RAID 5: It uses three or more disks with the equivalent of one disk holding parity information. If one disk fails, the RAID array will continue to operate. Of course, as you guessed it the performance will take a hit (slowness etc.)

RAID 6: It is same as RAID 5, except that the parity data is written to two drives (hence, at least one more drive compared to RAID 5).. resulting in added redundancy.

RAID 10: You will find this alternatively mentioned as RAID 1 + 0 in various technical documentations. It requires at least four disks but can support more as long as the total number is even. It will continue to operate even if multiple disks fail, as long as at least one drive in each mirror continues to function.

RAID Levels 2, 3, 4 and 7 - What's wrong with them?


                                                                RAID 2, 3, 4 and 7

Well they do exist.. but are not so common in most deployments.


Labels:

Comments

Post a Comment

Popular posts from this blog

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o...
Post a Comment
Read more

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account. ...
4 comments
Read more

MITRE ATT&CK - Understanding Kerberos (for Golden Ticket Attack)

Kerberos = Network Authentication Protocol used by AD environments Provides authentication by issuing tickets to authenticate users and allow them access to the services Tickets are distibuted by KDC (Key Distribution Center), which is typically a Domain Controller (DC) During initial authentication, a TGT (Ticket Granting Ticket) is a ticket asigned to a user by KDC. TGT is later used to authenticate the user to the KDC in order to request a service ticket from TGS (Ticket Granting Service). Service tickets are granted for authentication against services. List of steps / negotiations for Kerberos authentication (of the user with the service): The user requests  (AS-REQ)  a TGT from the KDC and the KDC verifies and validates the credentials and user information. This request if often done automatically at login. After authenticating the user, the KDC sends an encrypted TGT back to the requester  (AS-REP) . The user presents the TGT to the DC and requests a TGS  (TGS-...
Post a Comment
Read more