HP 635n Practical IPsec Deployment for Printing and Imaging Devices - Page 44

IPsec Basics: Receiving an IPsec Protected Packet

Page 44 highlights

Figure 38 - IPsec Although we know that this is a port 9100 print job, we have no way to tell when IPsec is used, nor can we capture any TCP 9100 packet data that isn't encrypted, play it back, or send it to another printer. IPsec Basics: Receiving an IPsec Protected Packet We can actually cover the last three bullets in this section! Yea! • IPsec checks the IPsec policy and determines that the packet needs to be protected by IPsec • IPsec checks the SADB and sees that there are no entries for this packet • IPsec calls on IKE to populate the SADB • IKE establishes an SA for itself by negotiating security parameters, exchanging secret key material, and mutually authenticating both endpoints (via Pre-Shared Key) • Using the SA negotiated by IKE between the initiator and responder, IKE then can safely negotiate two IPsec SAs (IKE Phase 2 also referred to as IKE Quick Mode), one for each data flow direction, and puts them in the SADB. NOTE: IKE populates the SADB on both the initiator and responder. • IPsec uses these entries to provide IPsec protection to the packet and sends the packet out on the network • The printer receives the IPsec protected packet and checks the SADB for a matching entry based upon the IP addresses and Security Parameters Index (SPI) • IPsec decrypts the packet and then checks the Security Policy to make sure the proper protection was used for the packet • IPsec strips off the IPsec headers and puts the packet back to normal Figure 38 shows the ESP Header close up. 44

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193

44
Figure 38 – IPsec
Although we know that this is a port 9100 print job, we have no way to tell when IPsec is used, nor
can we capture any TCP 9100 packet data that isn’t encrypted, play it back, or send it to another
printer.
IPsec Basics: Receiving an IPsec Protected Packet
We can actually cover the last three bullets in this section!
Yea!
IPsec checks the IPsec policy and determines that the packet needs to be protected by IPsec
IPsec checks the SADB and sees that there are no entries for this packet
IPsec calls on IKE to populate the SADB
IKE establishes an SA for itself by negotiating security parameters, exchanging secret key
material, and mutually authenticating both endpoints (via Pre-Shared Key)
Using the SA negotiated by IKE between the initiator and responder, IKE then can safely
negotiate two IPsec SAs (IKE Phase 2 also referred to as IKE Quick Mode), one for each data
flow direction, and puts them in the SADB. NOTE: IKE populates the SADB on both the
initiator and responder.
IPsec uses these entries to provide IPsec protection to the packet and sends the packet out on
the network
The printer receives the IPsec protected packet and checks the SADB for a
matching entry based upon the IP addresses and Security Parameters Index
(SPI)
IPsec decrypts the packet and then checks the Security Policy to make sure
the proper protection was used for the packet
IPsec strips off the IPsec headers and puts the packet back to normal
Figure 38 shows the ESP Header close up.