Did you notice that Juniper has updated their IDP policy templates?
First lets review the list of old of pre-defined templates..
blogger@SRX> show security idp policy-templates-list
Web_Server
DMZ_Services
DNS_Service
File_Server
Getting_Started
IDP_Default
Recommended
Lets check the version of that template..
blogger@SRX> show security idp security-package-version
Attack database version:2395(Wed Jul 2 18:14:04 2014 UTC)
Detector version :12.6.160140626
Policy template version :2192
Lets check and see whats available..
blogger@SRX> request security idp security-package download check-server
Successfully retrieved from(https://services.netscreen.com/cgi-bin/index.cgi).
Version info:2395(Detector=12.6.160140626, Templates=2395)
So you see, even if you are automatically updating the attack database that doesn't update the policy templates.
Showing posts with label IDP. Show all posts
Showing posts with label IDP. Show all posts
SRX IDP
This post will show you how to get IDP on an SRX100H going and tested
to be working.
I will be using a Trial licence which is valid for 30days.
1) GET AND INSTALL THE IDP LICENSE
a) First make sure you can ping a URL from your SRX
as the download process will use name lookups.
blogger@LEFTY> ping www.juniper.net inet
PING e1824.dscb.akamaiedge.net (184.87.23.148): 56 data bytes
64 bytes from 184.87.23.148: icmp_seq=0 ttl=54 time=33.373 ms
64 bytes from 184.87.23.148: icmp_seq=1 ttl=54 time=30.299 ms
64 bytes from 184.87.23.148: icmp_seq=2 ttl=54 time=29.531 ms
^C
--- e1824.dscb.akamaiedge.net ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 29.531/31.068/33.373/1.660 ms
If that doesn’t work, setup name servers in the config.
Subscribe to:
Posts (Atom)