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

IPsec Basics - printer cannot scan to network

Page 23 highlights

header. This attack is called Data Injection. Jane can accomplish this addition because TCP/IP has limited integrity checking - simple checksums. Because Jane is acting as a MITM, she can receive a packet and add data to it, then send it back out. The beauty of this approach is that the TCP/IP stack takes care of the new checksum automatically! The integrity of the packet was compromised, but in a hard to detect way. Jane automatically receives the secret document via email even though the MFP operator didn't send it to Jane's email address originally. If the email logs are viewed, it would appear that the person using Scan to Email on the MFP entered Jane's email address. IPsec Basics We've seen how our attacker Jane was able to access our MFP documents by taking advantage of the lack of confidentiality, mutual authentication, and integrity as well as some network infrastructure capabilities. We also know that these are general vulnerabilities and that any service on a TCP/IP network is subject to these attacks. What can we do to stop these attacks? One way is to deploy IPsec. What exactly is IPsec? Well, IPsec is a protocol suite that provides cryptographic protection to IP. The IPsec policy is a set of rules that determine which IP packets are provided this protection. Let's look at Figure 21 - Printing without an IPsec Policy. In this figure, we see a normal print job being sent to the printer. We also know that this data can be captured and manipulated by Jane in a in a variety of ways. Figure 21 - Printing without an IPsec Policy Now we want to deploy IPsec and see how IPsec works for printing. Let's look at the print data that is being transmitted by the computer first. Refer to Figure 22 - Printing with an IPsec Policy. 23

  • 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

23
header.
This attack is called Data Injection.
Jane can accomplish this addition because TCP/IP has
limited integrity checking – simple checksums.
Because Jane is acting as a MITM, she can receive a
packet and add data to it, then send it back out.
The beauty of this approach is that the TCP/IP stack
takes care of the new checksum automatically!
The integrity of the packet was compromised, but in a
hard to detect way.
Jane automatically receives the secret document via email even though the MFP
operator didn’t send it to Jane’s email address originally.
If the email logs are viewed, it would
appear that the person using Scan to Email on the MFP entered Jane’s email address.
IPsec Basics
We’ve seen how our attacker Jane was able to access our MFP documents by taking advantage of
the lack of confidentiality, mutual authentication, and integrity as well as some network infrastructure
capabilities.
We also know that these are general vulnerabilities and that any service on a TCP/IP
network is subject to these attacks.
What can we do to stop these attacks?
One way is to deploy
IPsec.
What exactly is IPsec?
Well, IPsec is a protocol suite that provides cryptographic protection to IP.
The IPsec policy is a set of rules that determine which IP packets are provided this protection.
Let’s
look at Figure 21 – Printing without an IPsec Policy.
In this figure, we see a normal print job being
sent to the printer.
We also know that this data can be captured and manipulated by Jane in a in a
variety of ways.
Figure 21 - Printing without an IPsec Policy
Now we want to deploy IPsec and see how IPsec works for printing.
Let’s look at the print data that
is being transmitted by the computer first.
Refer to Figure 22 – Printing with an IPsec Policy.