An of Firewall Technologies: Keywords
An of Firewall Technologies: Keywords
ii ii ii ii
Abstract
The iiincreasing iicomplexity iiof iinetworks, the iinetwork iithus iicaused iimakes iithe
iiand iithe iineed iito iimake iithem iimore iiopen
question iiof iisecurity iimore iicomplicated
iithan iihitherto, iiand iinecessitates iithe
iidue iito iithe iigrowing iiemphasis iion iiand
iifirewall.
iitechniques iifor iithe iiprotection iiof
iifirewall iitechnologies.
• Only authorised traffic, as
defined by the local security
Keywords: iiFirewall iitechnologies, policy, is allowed to pass
iinetwork iisecurity, iiaccess iicontrol, through it.
iisecurity iipolicy, iiprotective
• The iifirewall iiitself iiis iiimmune iito
iimechanisms.
iipenetration.
ii ii ii ii ii ii ii ii ii ii ii
1 Introduction
Today's iinetworks iichange iiand iidevelop
iion iia iiregular iibasis iito iiadapt iito iinew
iibusiness
Outside
iisituations,suchasreorganisations,acquisi
tions,outsourcing,mergers,joint
iiventures, iiand iistrategic iipartnerships,
1
iiprotecting iithe iipoints iiof iientry iiinto iithe iiTherearethreebasicapproachesor
iinetwork. iiAs iiFigure ii1 iishows, iia iifirewall iiservicesthat iiafirewallusesto iiprotect
iimay iiconsist iiof iia iivariety iiof iicomponents iianetwork: iipacket iifiltering, iicircuit iiproxy,
iiincluding iihost ii(called iibastion iihost), iirouter iiand iiapplication iiproxy ii[6, ii11]. iiSome
iifilters ii(or iiscreens), iiand iiservices. iiA iiauthors ii[13, ii10] iibroadly iiclassify iithese iiinto
iigateway iiis iia iimachine iior iiset iiof iimachines iitwo iikinds iiof iiapproach: iitransport iilevel iiand
iithat iiprovides iirelay iiservices iicomplementing iiapplication iilevel ii(by iiincluding iicircuit
iithe iifilters. iiAnother iiterm iiillustrated iiin iithe iiproxy iiin iithis iicategory).
iiThis iiis iian iiarea iior iisub-network iibetween iithe 2.1 Packet iifiltering
iiinside iiand iioutside iinetworks iithat iiis
Firewall iishaving iithis iifunction iiperform iionly
iipartially iiprotected. iiOne iior iimore iigateway
iivery iibasic iioperations, iisuch iias iiexamining
iimachines iimay iibe iilocated iiin iithe iiDMZ.
iithe iipacket iiheader, iiverifying iithe iiIP iiaddress,
iiExemplifying iia iitraditional iisecurity
iithe iiport iior iiboth, iiand iigranting iiand iidenying
iiconcept, iidefence-in- iidepth, iithe iioutside
iiaccess iiwithout iimaking iiany iichanges. iiDue
iifilter iiprotects iithe iigateway iifrom iiattack,
iito iithis iisimplicity iiof iioperation, iithey iihave
iiwhile iithe iiinside iigateway iiguards iiagainst
iithe iiadvantage iiof iiboth iispeed iiand iiefficiency.
iithe iiconsequences iiof iia iicompromised
iiThe iifiltered iipackets iimay iibe iiincoming,
iigateway ii[6, ii10]. iiDepending iion iithe
iioutgoing iior iiboth, iidepending iion iithe iitype iiof
iisituation iiof iithe iinetwork iiconcerned, iithere
iirouter. iiAn iiadditional iiadvantage iiis iithat iithey
iimay iibe iimultiple iifirewalls, iimultiple iiinternal
iido iithei iijob iiquiet iiindependently iiof iithe
iinetworks, iiVPNs, iiExtranets iiand iiperimeter
iiuser's iiknowledge iior iiassistance, iii.e., iithey
iinetworks. iiThere iimay iialso iibe iia iivariety iiof
iihave iigood iitransparency. iiPackets iican iibe
iiconnection iitypes, iisuch iias iiTCP iiand iiUDP,
iifiltered iion iithe iibasis iiof iisome iior iiall iiof iithe
iiaudio iior iivideo iistreaming, iiand iidownloading
iifollowing iicriteria: iisource iiIP iiaddress,
iiof iiapplets. iiDifferent iitypes iiof iifirewall
iidestination iiIP iiaddress, iiTCP/UDP iisource
iiconfiguration iiwith iiextensive iipractical
iiport, iiand iiTCP/UDP iidestination iiport. iiA
iiguides iican iibe iifound iiin ii[6, ii4]. iiThere iiare
iifirewall iiof iithis iitype iican iiblock iiconnections
iialso iimany iifirewall iiproducts iion iithe iimarket
iito iiand iifrom iispecific iihosts, iinetworks iiand
iifrom iidifferent iivendors. iiSee ii[9] iifor iian
iiports. iiThey iiare iicheap iisince iithey iiuse
iiupdated iilist iiof iiproducts iiand iivendors.
iisoftware iialready iiresident iiin iithe iirouter, iiand
iithem.
The iisecond iiapproach iiis iithe iiuse iiof iiwhat iiis
iicalled iia iicircuit iiproxy. iiThe iimain iidifference
2
The iithird iiapproach iiinvolves iithe iiuse iiof iioften iifind iithemselves iiworking
iiwhat iiis iiknown iias iian iiapplication iiproxy. iiAn iiagainst iimisconception iiand iipopular
iiapplication iiproxy iiis iimore iicomplicated iiin iiopinions iiformed iifrom iiincomplete
iioperation iithan iia iipacket iifiltering iifirewall iior iidata. iiSome iiof iithese iiopinions
iia iicircuit iiproxy. iiThe iiapplication iiproxy iispring iimore iifrom iihope iithan iifact,
iiunderstands iithe iiapplication iiprotocol iiand iisuch iias iithe iiidea iithat iiinternal
iidata, iiand iiintercepts iiany iiinformation iinetwork iisecurity iican iibe iisolved
iiintended iifor iithat iiapplication. iiOn iithe iibasis iisimply iiby iideploying iia iifirewall".
iiof iithe iiamount iiof iiinformation iiavailable iito iiWhile iiit iiis iitrue iithat iifirewalls iiplay
iimake iidecisions, iithe iiapplication iiproxy iican iian iiimportant iiand iicentral iirole iiin
iiauthenticate iiusers iiand iijudge iiwhether iiany iithe iimaintenance iiof iinetwork
iiof iithe iidata iicould iipose iia iithreat. iiThe iiprice iisecurity iiand iiany iiorganisation iithat
iito iibe iipaid iifor iithis iimore iicomprehensive iiignores iithem, iidoes iiso iiat iiits iiperil,
iifunction iiis iithat iiusers iior iiclients iioften iihave iithey iiare iineither iithe iipanacea iiof
iito iibe iireconfigured iito iithem, iisometimes iia iievery iisecurity iiaspect iiof iia iinetwork,
iicomplicated iiprocess, iiwith iia iiconsequent iinor iithe iisole iisufficient iibulwark
iiare iireferred iito iias iiproxy iiservices, iiand iithe iifirewalls iican't iido iiis iias iiimportant
iihost iimachines iirunning iithem iias iiapplication iias iiknowing iiwhat iithey iican. iiThe
3
iito iiimprove iiperformance, iiand iisupport iivendors, iiisa iicritical iiproblem. iiAs iimore iiand
iiVirtual iiPrivate iiNetwork ii(VPNs), iiWeb- iimore iisecurity iiservices iiare iiintroduced iiand
iiThere iiis iialso iia iitendency iito iiadd iinon- iiproperly iiconfiguring iiand iimaintaining iithe
security- iirelated iifunctions iito iithe iifirewall iiservices iiconsistently iibecomes iiincreasingly
iisuch iias iibuilt-inWebservers, iiFTP iiservers, iidifficult. iiAn iierror iiby iian iiadministrator iiin
iiand iie-mail iisystems, iiand iieven iiproxy iimaintaining iia iiconsistent iiconfiguration iiof
iiservers iifor iistreaming iiaudio iiand iivideo. iisecurity iiservices iican iieasily iilead iito iisecurity
We iiagree iiwith iithose iiwho iifeel iithat iisome iiprovide iia iisecurity iimanagement iiinterface
iiadditions iito iifirewalls iimake iisense iiand iiare iithat iienables iiit iito iibe iilocally iior iiremotely
iiuseful iiwhen iithey iienhance iisecurity, iiwhile iimanaged iiin iia iicoherent iiand iicomprehensible
iiincrease iiin iivulnerability. iiFor iiexample, iito 3.4 Virtual iiPrivate iiNetworks ii(VPNs)
iiadd iiservices iithat iiincrease iithe A iiVPN iiis iian iiencrypted iitunnel iiover iithe
iiadministration iiload iiadds iianother iipotential iiInternet iior iianother iiuntrusted iinetwork
While caching is not traditionally a function ii(reasonable iiextension) iito iisecure iinetworks,
of firewalls, iiit iiis iibecoming iian iiincreasingly iiso iithat iithey iican iisafely iicommunicate iiin
iifrequent iiand iiimportant iifeature. iiAn iiincrease iiprivate iiover iithe iipublic iinetwork. iiThey
iiin iiperformance iiis iiachieved iiby iicaching iithe iiachieve iithis iiby iistrong iiauthentication iiand
iicontents iiof iian iiaccessed iilocation iiwith iithe iiencryption iiof iiall iitraffic iibetween iithem.
iiwill iilead iito iialready iicached iicontents iibeing 3.5 Adaptive iiFirewalls
iiused, iiwithout iiit iibeing iinecessary iito iiaccess
The iinew iitrend iiis iitowards iiadaptive iifirewalls
iithe iilocation iiagain ii(except iiwhen iiit iiis
iithat iitie iifilters, iicircuit iigateways iiand iiproxies
iinecessary iito iirefresh).
iitogether iiin iiseries ii[2]. iiThis iigives iithe
3.2 Logging iiand iiAlerts iithe iilevel iiof iisecurity iiused iifor iidifferent
It iiis iiimportant iifor iia iifirewall iito iilog iievents, iiservices iior iiat iidifferent iipoint iisin iithe iiuse iiof
iidetermine iitheir iilegitimacy iior iiotherwise, iithose iiservices. iiHe iimay, iifor iiexample,
iiand iinotify iithe iinetwork iiadministrator. iiIt iiconfigure iithe iifirewall iito iigive iipriority iito
iishould iibe iinoted iithat iiit iiis iiessential iito iispeed iiof iitransfer iiat iithe iiexpense iiof iisecurity
iiprotect iithe iiintegrity iiof iithe iilog, iisince iiwhen iithis iiis iiappropriate. iiThe iifirewall iiwill
iiunauthorised iiaccess iito, iiand iiediting iiof, iithe iithen iion iisuch iioccasions iireduce iisecurity iito iia
iilog iiwill, iiof iicourse, iineutralise iiits iiraison iilower iilevel, iithus iiallowing iifor iigreater iispeed
iid’être. iiWhether iithe iifunction iiof iiprotecting iiof iitransfer, iiand iireturn iiit iito iiits iioriginal
iithe iilog iiis iifulfilled iiby iithe iifirewall iiitself iior iilevel iion iicompletion iiof iithe iitransfer.
4
ii the iinetwork iiinterface. iiTherefore iithere iiare iiregularly iinew iipolicies
iito iibe iienforced, iiand, iito iiremain iieffective,
iihandled iiby iiInternet iirouters, iiwhile iiothers 4.1 Trends iiThreatening iiFirewalls
iiinsist iithat iithis iiis iia iimatter iiof iiaccess iicontrol,
Common iinetwork iidenial iiof iiservice iiattacks
iiand iithus iishould iibe iiincluded iiin iithe iifirewall.
iiinclude iimail iibombs, iiping iifloods, iiand
There iiare iitwo iilevels iiof iinetwork iipolicy iithat iiof iiall iibreaches iitoday iiare iiperpetrated iiby
iidirectly iiinfluence iithe iidesign, iiinstallation iisome iilegitimate iiuser iialready iibehind iithe
iiformer iiis iithe iinetwork iiservice iiaccess The iitraditional iiassumption iithat iiall iiinside
iipolicy, iiwhich iilays iidown iiwhich iiservices iithe iifirewall iiare iifriendly iiand iiall iioutside iiit
iiare iito iibe iiaccessible iito iiwhom, iiand iihow iipotentially iihostile, iiis iinow iibecoming
iithey iiare iito iibe iiused. iiThe iilatter iiis iithe iisomewhat iioutdated. iiInternet iiconnectivity
iifirewall iidesign iipolicy, iiwhich iidescribes iihas iiexpanded, iiExtranets iican iiallow
iihow iithe iifirewall iiwill iiimplement iithe iioutsiders iiaccess iito iiareas iiprotected iiby
Service iiaccess iipolicy iimay, iifor iiexample, In iithe iiliterature ii[3], iisome iipeople iihave iigone
iidecree iithat iithere iishall iibe iino iiaccess iito iia iiso iifar iias iito iisuggest iithat iia iimore iiadaptive
iisite iifrom iithe iiInternet, iibut iiallow iiaccess iiapproach iiwould iibe iito iidrop iifirewalls
iifrom iithe iisite iito iithe iiInternet. iiAlternatively, iialtogether iion iithe iibasis iithat iithey iiare
iiit iimay iidecree iithat iiaccess iifrom iithe iiInternet iiobsolete, iior iithat iithe iiuse iiof iicryptography
iishall iibe iirestricted iito iicertain iiselected iiobviates iithe iineed iifor iithem. iiBellovin ii[3]
iiservices iiin iithe iisite. iiThe iilatter iiis iithe iimore iidisagrees iiwith iithis iiview, iiand iiso iido iiwe.
5
iicode ii- iiin ii1998, ii9 iiof ii13 iiCERT iiadvisories iibut iia iifew, iithat iiillustrate iithis iipoint iiare:
iiconcerned iibuffer iioverflows iiand iitwo iiof iithe • The iiproposal iiof iia iidistributed iifirewall ii[3],
iirest iiwere iicryptographic iibugs ii- iiand iicannot iiusing iiIPSEC ii(IP iiSecurity), iia iipolicy
iibe iiprevented iiby iiencryption iior iilanguage, iiand iisystem iimanagement iitools,
iiauthentication. iiA iifirewall iishields iimost iithat iipreserves iicentral iicontrol iiof iiaccess
iisuch iiapplications iifrom iihostile iiconnections. iipolicy iiwhile iireducing iior iieliminating iiany
iiprovide iitheir iiown, iithere iiare iitoo iimany iiadapting iicontrol iiof iinetwork iiaccess, iithus
iiolder iiprotocols iiand iiimplementations iithat iiestablishing iian iieffective iinetwork iisecurity
iido iinot. iiSaying iithat iistrong iicryptography iipolicy iiby iiexamining iievery iipacket iiand
iishould iibe iiused iiis iitrue iibut iiirrelevant. iiIn iithe iiadapting iirules ii"on-the-fly" iibased iion
iicontext iiof iisuch iiapplications, iiit iiis iisimply iiinformation iiin iithe iipacket iipassing iithrough
iiunavailable.
iithe iinetwork iiinterface.
• More iisubtly, iifirewalls iiare iia iimechanism iifor • FORE iiSystems' iiFirewall iiSwitching
iipolicy iicontrol. iiThat iiis, iithey iipermit iia iisite's
iiAgent[8], iiin iicombination iiwith iiCheck
• OMG's[15]CORBAFirewallSecurity[13],
As iialready iistated, iiwe iiconcur iiwith iithe iiwhichbringsfirewallsto iidistributed iiobject
iiabove, iiand iicite iithe iifollowing iiadditional
iitechnology iiand iiprovides iia iistandard
iiarguments.
iiapproach iiby iiwhich iiha iifirewall iiidentifies
6
iidevelopment iitrends iithat iithreaten iithem,
iithey iiare iistill iia iipowerful iiprotective
References
1. http://www.crossnodes.com/icsa/
perimeter.html ii
2. http://www.checkpoint.com/products/
whitepapers/wp30.pdf
7
9