Symantec 360R Administration Guide - Page 68

Defining inbound access

Page 68 highlights

68 Network traffic control Defining inbound access Defining inbound access Inbound rules control the type of traffic flowing into application servers on your appliance-protected networks. The default state for inbound traffic is that all traffic is denied (automatically blocked) until you configure inbound rules for each kind of traffic you want to allow. If the inbound traffic contains a protocol or application that is not part of an enabled rule, the connection request is denied and logged. The appliance supports a maximum of 25 inbound rules. When creating inbound rules, you must specify the applications server, the service, protocols, and ports that the rule allows, and source and destination information for each rule. When an inbound rule exists, any external host can successfully pass inbound traffic matching the rule. Inbound rules redirect traffic that arrives on the WAN ports to another internal server on the protected LAN. For example, an inbound rule enabled for HTTP results in all HTTP traffic arriving on the WAN port to be redirected to the server specified as the HTTP application server. You must define the server before using it in a rule. Inbound rules are not bound to a computer group. To define inbound access To stop the configuration process, click Cancel at any time while configuring computers. To clear all the information from the tab, click Clear Form at any time. See "Inbound Rules field descriptions" on page 180. To define a new inbound rule 1 In the SGMI, in the left pane, click Firewall. 2 To create a new rule, in the right pane, on the Inbound Rules tab, under Rule Definition, in the Name text box, type a unique name for the inbound rule. 3 Check Enable Rule. 4 In the Application Server drop-down list, select a defined computer. Computers are defined on the Computers tab in the Firewall section. 5 On the Service drop-down list, select an inbound service. 6 Click Add. The configured rule is displayed in the Inbound Rules List. To update an existing inbound rule 1 In the left pane, click Firewall.

  • 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
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218

68
Network traffic control
Defining inbound access
Defining inbound access
Inbound rules control the type of traffic flowing into application servers on your
appliance-protected networks. The default state for inbound traffic is that all
traffic is denied (automatically blocked) until you configure inbound rules for
each kind of traffic you want to allow. If the inbound traffic contains a protocol
or application that is not part of an enabled rule, the connection request is
denied and logged. The appliance supports a maximum of 25 inbound rules.
When creating inbound rules, you must specify the applications server, the
service, protocols, and ports that the rule allows, and source and destination
information for each rule. When an inbound rule exists, any external host can
successfully pass inbound traffic matching the rule.
Inbound rules redirect traffic that arrives on the WAN ports to another internal
server on the protected LAN. For example, an inbound rule enabled for HTTP
results in all HTTP traffic arriving on the WAN port to be redirected to the
server specified as the HTTP application server. You must define the server
before using it in a rule.
Inbound rules are not bound to a computer group.
To define inbound access
To stop the configuration process, click Cancel at any time while configuring
computers.
To clear all the information from the tab, click Clear Form at any time.
See
“Inbound Rules field descriptions”
on page 180.
To define a new inbound rule
1
In the SGMI, in the left pane, click
Firewall
.
2
To create a new rule, in the right pane, on the Inbound Rules tab, under Rule
Definition, in the Name text box, type a unique name for the inbound rule.
3
Check
Enable Rule
.
4
In the Application Server drop-down list, select a defined computer.
Computers are defined on the Computers tab in the Firewall section.
5
On the Service drop-down list, select an inbound service.
6
Click
Add
.
The configured rule is displayed in the Inbound Rules List.
To update an existing inbound rule
1
In the left pane, click
Firewall
.