SECURING FIBRE CHANNEL FABRICS - Brocade

More documents

Recommendations

Info

Chapter 8: Securing FOS-Based FabricsRole NameChassis-rolepermissionFirst inFOSDuties6.2.0 Chassis-specificconfigurationFabricAdmin 5.2.0 Fabric and switchadministrationOperator 5.2.0 General switchadministrationSecurityAdmin 5.3.0 SecurityadministrationSwitchAdmin 5.0.0 Local switchadministrationRole permission only andapplied to the useraccount through theuserConfig commandAll switch and fabriccommands, excludesuser management andAD commandsRoutine switchmaintenance commandsAll switch security anduser managementfunctionsMost switch (local)commands, excludingsecurity, usermanagement, andzoning commandsUser All Monitoring only Non-administrative usesuch as monitoringsystem activityZoneAdmin 5.2.0 ZoneadministrationDescriptionZone managementcommands onlyOther Password-Related FeaturesIt is possible to bypass the normal login procedure to recover a passwordby bringing the switch into single-user mode and obtainingspecial password recovery code from Brocade. This may be viewed asa security hole in some environments. To prevent unauthorized usersfrom entering a switch into single-user mode, a password can be seton the boot PROM. A recovery string can also be defined in case theboot PROM password is lost, to allow Brocade to recover the password.WARNING: If the boot PROM password is set and forgotten and there isno recovery string defined (or it is also forgotten), then there is no wayof regaining management access to the switch if the admin or rootpasswords are lost.142 Securing Fibre Channel Fabrics
FC-Specific SecurityFC-Specific SecurityBrocade has developed several FC-specific security features thatwould not normally be available in a conventional LAN. For example,devices connecting to a Fibre Channel fabric can be authenticatedusing a strong protocol with the DCC policy.FC Port Access ManagementThe FC ports on a switch are particularly vulnerable for several reasons.They can be used to introduce unauthorized devices into thefabric, such as another FC switch. They can also be used to connect anauthorized device prematurely, for example, before an HBA has beenconfigured, which may cause unexpected switch behavior.The simplest method of protecting unused FC ports is to disable them.Use the portDisable command, but note that port status changes do notsurvive reboots. Changes using the persistentPortDisable command, onthe other hand, persist and survive reboots.An additional layer of defense that can be used to prevent unauthorizedswitches from joining a fabric is to disable the ability of an FC portto become an E_Port using the portCfgPort command.Single Point of Management AccessManaging an FOS-based fabric by default can be performed from anyswitch. However, it is always simpler to secure one entry point than tosecure multiple entry points, and this rule applies to FC fabrics as well.In large fabrics made up of numerous FC switches, there are many possiblemanagement points that all need to be secured properly. To createa single point of control for fabric management, Brocade introduced theFCS policy in FOS 5.3.0. The FCS policy identifies one switch as the primarypoint of control (the fabric configuration server) to manage allswitches in the fabric. Administrators must perform changes to zoning,user accounts, passwords, or policies via the primary FCS, therebyreducing the number of possible entry points for a potential attacker.The FCS policy can be defined using the secPolicyCreate command(secPolicyCreate "FCS_POLICY", "member ;…;"member"),where the “member” is the switch domain ID.Example:switch:admin> secpolicycreate "FCS_POLICY", "2;4"FCS_POLICY has been createdSecuring Fibre Channel Fabrics 143
Page 1 and 2:
SECURINGFIBRECHANNELFABRICSSECOND E
Page 3:
SECURINGFIBRECHANNELFABRICSSECOND E
Page 6 and 7:
© 2012 Brocade Communications Syst
Page 8 and 9:
viSecuring Fibre Channel Fabrics
Page 10 and 11:
viiiSecuring Fibre Channel Fabrics
Page 12 and 13:
ContentsChapter 4: Security Basics
Page 14 and 15:
ContentsIsolation and Separation ..
Page 16 and 17:
ContentsxivSecuring Fibre Channel F
Page 18 and 19:
Chapter 1: Introduction• The Euro
Page 20 and 21:
Chapter 1: IntroductionThe SAN Secu
Page 22 and 23:
Chapter 1: IntroductionInternet sta
Page 24 and 25:
Chapter 1: Introductionoften, the s
Page 26 and 27:
Chapter 2: SAN Security MythsSAN Se
Page 29 and 30:
SAN Security Myth Number 5SAN Test
Page 31 and 32:
SAN Security Myth Number 6To demons
Page 33 and 34:
SAN Security Myth Number 7SAN Secur
Page 35 and 36:
SAN Basics for SecurityProfessional
Page 37 and 38:
Evolution of the FC ProtocolTable 1
Page 39 and 40:
Fibre Channel BasicsTable 2. FC pro
Page 41 and 42:
Fibre Channel BasicsFC FabricsFC fa
Page 43 and 44:
Fibre Channel BasicsType Category N
Page 45 and 46:
FC Fabric Features and ServicesAn F
Page 47 and 48:
FC Fabric Features and Servicesing
Page 49 and 50:
FC Fabric Features and ServicesWhen
Page 51 and 52:
FC Fabric Features and ServicesAnd
Page 53 and 54:
FC Fabric Features and ServicesSwit
Page 55 and 56:
FC Fabric Features and ServicesAs c
Page 57 and 58:
FC Fabric Features and ServicesSwit
Page 59 and 60:
FC Fabric Features and Servicesothe
Page 61 and 62:
Security Basics forStorage Professi
Page 63 and 64:
Security Modelshave enacted such le
Page 65 and 66:
Security Modelssures must be taken
Page 67 and 68:
Types of ThreatsTypes of ThreatsA t
Page 69 and 70:
Types of ThreatsOne significant thr
Page 71 and 72:
Types of Threatsside attacks such t
Page 73 and 74:
Types of Threatsences from previous
Page 75 and 76:
AttacksAttacksAttackers have many o
Page 77 and 78:
Attackstion between the two parties
Page 79 and 80:
Identification and AuthenticationBi
Page 81 and 82:
Physical SecurityOne challenge with
Page 83 and 84:
Physical SecurityPhysical access co
Page 85 and 86:
Information Disposal and Sanitizati
Page 87 and 88:
Chapter SummaryAlgorithm Passes Des
Page 89 and 90:
Elementary Cryptography5This chapte
Page 91 and 92:
Common Cryptography TermsHere are s
Page 93 and 94:
Symmetric vs. Asymmetric Cryptograp
Page 95 and 96:
Cryptographic Algorithms• Range o
Page 97 and 98:
Cryptographic AlgorithmsHashing alg
Page 99 and 100:
Modes of Operationencryption proces
Page 101 and 102:
Modes of OperationRSAAt around the
Page 103 and 104:
Key ManagementSSL can be used with
Page 105 and 106:
Key ManagementBrocade Encryption De
Page 107 and 108: FC Security Best Practices6In previ
Page 109 and 110: The Brocade SAN Security ModelThe m
Page 111 and 112: The Brocade SAN Security ModelStora
Page 113 and 114: The Brocade SAN Security ModelChann
Page 115 and 116: The Brocade SAN Security Modelrestr
Page 117 and 118: The Brocade SAN Security Modeltem a
Page 119 and 120: The Brocade SAN Security ModelPassw
Page 121 and 122: The Brocade SAN Security ModelData
Page 123 and 124: The Brocade SAN Security ModelWith
Page 125 and 126: Encrypting Data-in-FlightEncrypting
Page 127 and 128: Encrypting Data-at-RestEncrypting D
Page 129 and 130: Encrypting Data-at-Restand disk dev
Page 131 and 132: Encrypting Data-at-RestPhysical Sec
Page 133 and 134: Encrypting Data-at-RestTraining and
Page 135 and 136: Chapter SummaryChapter SummaryAltho
Page 137 and 138: Deploying SAN-AttachedDevices in a
Page 139 and 140: Securing the Servers in the DMZpoli
Page 141 and 142: Securing the Storage DevicesFor exa
Page 143 and 144: Securing the Storage DevicesInterne
Page 145 and 146: Auditing and Assessing the SANAudit
Page 147 and 148: Securing FOS-Based Fabrics8When it
Page 149 and 150: Securing Management InterfacesThe f
Page 151 and 152: Securing Management InterfacesThe t
Page 153 and 154: Securing Management InterfacesFilte
Page 155 and 156: Securing Management InterfacesThe f
Page 157: Securing Management Interfacesadmin
Page 161 and 162: FC-Specific SecurityBrocade-support
Page 163 and 164: FC-Specific SecurityTo prevent this
Page 165 and 166: Fabric-Based Encryptionthe Brocade
Page 167 and 168: Fabric-Based Encryption3. (LDAP onl
Page 169 and 170: Chapter SummaryInsistent Domain IDI
Page 171 and 172: Compliance and Storage9Certainly, m
Page 173 and 174: Payment Card Industry Data Security
Page 175 and 176: Breach Disclosure LawsThe precedent
Page 177 and 178: Gramm-Leach-Bliley Act (GLBA)vides
Page 179 and 180: Federal Information Processing Stan
Page 181 and 182: Common Criteria (CC)allow different
Page 183 and 184: Defense Information Systems Agency
Page 185 and 186: Other SAN Security Topics10SAN secu
Page 187 and 188: The Future of Key ManagementThe Fut
Page 189 and 190: Brocade Data EncryptionProducts11Br
Page 191 and 192: Brocade Encryption for Data-At-Rest
Page 193 and 194: Brocade Encryption for Data-At-Rest
Page 195 and 196: Brocade Encryption Features• Data
Page 197 and 198: Brocade Encryption FeaturesThe next
Page 199 and 200: Brocade Encryption FeaturesDEK clus
Page 201 and 202: Brocade Encryption Featuresthe DEK
Page 203 and 204: Brocade Encryption FeaturesThe foll
Page 205 and 206: Brocade Encryption InternalsFigure
Page 207 and 208: Design and Implementation Best Prac
Page 209 and 210:
Design and Implementation Best Prac
Page 211 and 212:
Brocade Encryption for Data-In-Flig
Page 213 and 214:
Chapter SummarySite ACiphertextSite
Page 215 and 216:
Fabric OS SecurityFeatures MatrixAL
Page 217 and 218:
Security FeatureFOS2.xFOS3.xFOS4.x+
Page 219 and 220:
Security FeatureFOS2.xFOS3.xFOS4.x+
Page 221 and 222:
Standards Bodies andOther Organizat
Page 223 and 224:
IETFSpecifically, the SNIA Security
Page 225 and 226:
IndexNumerics3DES 4Aaccess control
Page 227 and 228:
Indexhuman threat 9Iidentification
show all

SECURING FIBRE CHANNEL FABRICS - Brocade

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?