HP CM8000 Practical IPsec Deployment for Printing and Imaging Devices - Page 46

IPsec Guidelines for Printing and Imaging Devices

Page 46 highlights

Figure 40 - IPsec Packet Reception In Figure 40, we are going to start at the bottom and work our way up. The IPsec packet is received and values are extracted from the IP header (Source IP, Destination IP, etc...) and the SPI value is extracted from the IPsec header. Using these parameters, the SADB can be indexed to find an SADB entry. If there is no entry, the packet is dropped. If there is an entry, then the IPsec packet can be decoded and checked to make sure the proper protection was followed according to the IPsec Policy. Internally, the packet can be stripped of all the IPsec information and passed to the application as if nothing had happened. That is all there is to IPsec when using Pre-Shared Key authentication for the initiator and receiver. Remember, Pre-Shared key is not recommended for production environments. We are using it primarily to showcase what IPsec can do and to learn about IPsec. Although there are two more authentication mechanisms to cover, we know enough about IPsec to cover IPsec Policy deployment recommendations (finally!). IPsec Guidelines for Printing and Imaging Devices We need to be able to deploy IPsec in an enterprise printing and imaging environment and meet these goals: • Provide proper protection to protocols as referenced by the company's security policy • Provide proper protection to these protocols without bringing down the network or creating an unavailable service for the devices that require it. An incorrectly deployed IPsec policy can easily bring a network/service down. 46

  • 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

46
Figure 40 – IPsec Packet Reception
In Figure 40, we are going to start at the bottom and work our way up.
The IPsec packet is received
and values are extracted from the IP header (Source IP, Destination IP, etc…) and the SPI value is
extracted from the IPsec header.
Using these parameters, the SADB can be indexed to find an SADB
entry.
If there is no entry, the packet is dropped.
If there is an entry, then the IPsec packet can be
decoded and checked to make sure the proper protection was followed according to the IPsec Policy.
Internally, the packet can be stripped of all the IPsec information and passed to the application as if
nothing had happened.
That is all there is to IPsec when using Pre-Shared Key authentication for the initiator and receiver.
Remember, Pre-Shared key is not recommended for production environments.
We are using it
primarily to showcase what IPsec can do and to learn about IPsec.
Although there are two more
authentication mechanisms to cover, we know enough about IPsec to cover IPsec Policy deployment
recommendations (finally!).
IPsec Guidelines for Printing and Imaging Devices
We need to be able to deploy IPsec in an enterprise printing and imaging environment and meet
these goals:
Provide proper protection to protocols as referenced by the company’s security policy
Provide proper protection to these protocols without bringing down the network or creating
an unavailable service for the devices that require it.
An incorrectly deployed IPsec policy
can easily bring a network/service down.