Pages

Wednesday, May 27, 2015

2015 Canada IT Skills & Salary Report


Global Knowledge and Windows IT Pro with some other partners executed the 2015 IT Skills and Salary Suvery between Sept. 15 to Oct .24, 2014. Full pdf can be download from 2015 IT Skills & Salary Report


Here are some highlights which caught my eye balls:

1. Base Salary of Participants raised from 2011's $79,579 to 2015's $89,891


2. Salary by functional area. 

IT architecture is highest.


3.  Canadian Regional Variations

Alberta is leading in all areas


 4. Top 20 Highest-paying Certifications



5. Technology Areas of Interest for 2015




Reference:

1. 2015 IT Skills & Salary Report

Industry's Fastest Firewall - Juniper SRX5800 Delivers Two Terabits Throughput

Juniper SRX5800 delivers two terabits per second of throughput:


On Apr 15, 2015, Juniper Announced: Industry's Fastest Firewall - SRX5800 delivers two terabits per second of throughput




The first of its kind, the SRX data center firewall delivers the highest known performance on a single chassis with as low as 7 microseconds latency and 2 Tbps* performance — perfect for environments where security must operate at the speed of the network.





SRX5800 2 Tbps Test by Ixia - live demo:






Reference: http://www.juniper.net/us/en/dm/bettersecurity/





Tuesday, May 12, 2015

Installation of Junos Space Security Director and Managing Juniper Firewall

Previous Background Posts for JunOS Space


Junos Space Security Director (previously known as Security Design) is  an application on the Junos Space platform, which manages Networks SRX Series Services Gateways.

It helps administrators quickly manage all phases of security policy life cycle for stateful firewall, security intelligence (leveraging threat feeds from Spotlight Secure cloud for protection against Web application attacks, command and control related threats, botnets, and local data feeds), unified threat management (UTM), intrusion prevention system (IPS), AppFW, VPN, and Network Address Translation (NAT).

Junos Space is Juniper’s comprehensive network management solution that simplifies and automates management of Juniper’s switching, routing, and security devices. It includs:
In this instruction post, Junos Space Security Director will be added into JunOS Space Network Management Platform installed in previous post. It will be used to manage one vSRX, which also installed in prevous post.


1. Download Security Director installation image for JunOS Space

It can be downloaded from JunOS Software Download site.

2. Add it into Administration - Applications

Choose Upload via HTTP button and browse to the download folder. You will need a 64M Security-Director.14.1R2.6.img file. 

3. Check it from Jobs - Job Management

After confirmed Security Director added into Space, install it from Administration->Applications->Add Application place. Click install button beside Upload via SCP button. During installation, you can check the progress from Jobs->Job Management window as show below:

4. Security Director Installed

The installation process will take 10-15 minutes depending on the speed of your device. After Security Director image installed, you should be able to reach from the top of applications dropdown menu.


5. Manage vSRX Policy (to be continued) Part3


5.1 Import vSRX policy
5.2 Change Policy
5.3 Publish and Update

Reference:

a. Security Director User Guide - Juniper Networks

Sunday, May 10, 2015

Juniper vSRX Firewall (Firefly Perimeter) installation in ESXi and Managed by JunOS Space

For how to Install JUNOS Space Virtual Appliance at ESXi 5.5, please check my previous posts:.

Juniper Firefly Perimeter, also called vSRX is a virtual firewall from Juniper’s SRX product line. Firefly Perimeter provides security and networking services at the perimeter in a virtualized private or public cloud environments. It runs as a virtual machine on a standard x86 server  and delivers similar security and networking features available on branch SRX Series appliance. The vSRX virtual firewall is with a complete and integrated virtual security solution, including core firewall, robust networking, advanced security services at Layers 4–7, and automated lifecycle management capabilities for enterprises and service providers alike. It is also able to managed by JunOS Space Network Management Platform with Security Director Application.

This following instructions are how it is being installed into ESXi 5.5 virtual lab environment and also how it integrated with JunOS Space Network Management Platform.

1. Topology

PC with ip address 192.168.2.20 is using browser to access JunOS Space (192.168.2.72 - Web GUI Interface eth0.0 IP address).
JunOS Space is using Device Management Interface eth3 (172.17.3.70) to manage vSRX through vSRX's ge-0/0/1.



2. Download Firefly Perimeter (vSRX)

If you have license, you could download Firefly Perimeter from Juniper Supprt Site. For 60 days evaluation version, please download from here.

You can use an evaluation license to explore the Firefly Host product. The evaluation product is fully functional, and it has an embedded thirty-day license. This license will be removed after you save your first purchased license information in the wizard.

If no purchases license information is saved, after 30 days, the status turns Red for Firefly Host VM, IDS and AV and says License Expired. Also, every twenty four hours, a high security alert is displayed saying The 30 Day trial period has expired. A purchased license is required to be input in Settings->Status & License. However, no functionality is blocked and the system continues to work as before.



3. Deploy OVF Template in ESXi 5.5

Select junos-vsrx-12.1X47-D20.7-domestic.ova. After deployment, you could check settings and add more interface as you needed.

4. Start vSRX virtual machine. 

Log in by user account root without password.

5. Basic Configuration on vSRX

There are some basic configuration such as root password, interface ip addresses, zone interface and services.

root> show configuration
## Last commit: 2015-05-10 20:02:32 UTC by root
version 12.1X47-D20.7;
system {
    root-authentication {
        encrypted-password "$1$x20k81NM$wphXL5F5Y10fRwNZp44nf."; ## SECRET-DATA
    }
    services {
        ssh {
            max-sessions-per-connection 32;
        }
        netconf {
            ssh;
        }
        web-management {
            http {
                interface ge-0/0/0.0;
            }
        }
    }
    syslog {
        user * {
            any emergency;
        }
        file messages {
            any any;
            authorization info;
        }
        file interactive-commands {
            interactive-commands any;
        }
        file default-log-messages {
            any info;
            match "(requested 'commit' operation)|(copying configuration to juniper.save)|(commit complete)|ifAdminStatus|(FRU power)|(FRU removal)|(FRU insertion)|(link UP)|transitioned|Transferred|transfer-file|(license add)|(license delete)|(package -X update)|(package -X delete)|(FRU Online)|(FRU Offline)|(plugged in)|(unplugged)|GRES";
            structured-data;
        }
    }
    license {
        autoupdate {
            url https://ae1.juniper.net/junos/key_retrieval;
        }
    }
}
interfaces {
    ge-0/0/0 {
        unit 0 {
            family inet {
                address 192.168.2.80/24;
            }
        }
    }
    ge-0/0/1 {
        unit 0 {
            family inet {
                address 172.17.3.80/24;
            }
        }
    }
}
snmp {
    trap-group space {
        targets {
            172.17.3.70;
        }
    }
}
routing-options {
    static {
        route 0.0.0.0/0 next-hop 192.168.2.1;
    }
}
security {
    screen {
        ids-option untrust-screen {
            icmp {
                ping-death;
            }
            ip {
                source-route-option;
                tear-drop;
            }
            tcp {
                syn-flood {
                    alarm-threshold 1024;
                    attack-threshold 200;
                    source-threshold 1024;
                    destination-threshold 2048;
                    queue-size 2000; ## Warning: 'queue-size' is deprecated
                    timeout 20;
                }
                land;
            }
        }
    }
    policies {
        from-zone trust to-zone trust {
            policy default-permit {
                match {
                    source-address any;
                    destination-address any;
                    application any;
                }
                then {
                    permit;
                }
            }
        }
        from-zone trust to-zone untrust {
            policy default-permit {
                match {
                    source-address any;
                    destination-address any;
                    application any;
                }
                then {
                    permit;
                }
            }
        }
        from-zone untrust to-zone trust {
            policy default-deny {
                match {
                    source-address any;
                    destination-address any;
                    application any;
                }
                then {
                    deny;
                }
            }
        }
    }
    zones {
        security-zone trust {
            tcp-rst;
            host-inbound-traffic {
                system-services {
                    all;
                }
            }
            interfaces {
                ge-0/0/1.0;
            }
        }
        security-zone untrust {
            screen untrust-screen;
            interfaces {
                ge-0/0/0.0 {
                    host-inbound-traffic {
                        system-services {
                            http;
                            https;
                            ssh;
                            telnet;
                            dhcp;
                        }
                    }
                }
            }
        }
    }
}

6. JunOS Space Configuration

6.1 Add 172.17.3.80 into Discover Target





 6.2 Discovered Device

 6.3 Confirm vSRX managed by JunOS Space






Reference:

1. Junos®Space Network Management Platform User Guide

Saturday, May 9, 2015

Install JUNOS Space Virtual Appliance at ESXi 5.5

Juniper NSM (Network Security Management) will be end of life for support on Nov 29 2015.

ProductEOL
Announced
Last OrderLast Date to
Convert Warranty
Same Day Support
Discontinued
Next Day Support
Discontinued
End of
Support
NSMXpress, NSM 300001/30/201507/31/201507/31/201607/31/201707/31/201907/31/2020
NS-SM-A2-CM, NS-SM-A2-HA05/13/201410/31/201410/31/201510/31/201610/31/201810/31/2019
NS-SM-A-BSE, NS-SM-A-CM, NS-SM-A-HA06/01/201011/29/201011/29/201111/29/201211/29/201411/29/2015

Junos Space is the next comprehensive network management solution that simplifies and automates management of Juniper’s switching, routing, and security devices. Junos Space Network Management Platform works with other management applications to deliver comprehensive management of Juniper devices including:
  • Edge Services Director
  • Security Director
  • Services Activation Director
  • Network Director
  • Service Now
  • Service Insight
  • Content Director
  • Virtual Director
In this post, detailed steps with screenshots will present you a easy guide to install a JunOS Space Virtual Appliance into Vmware ESXi 5.5.

1. Download space-14.1R2.9.ova 

Download OVA file from Juniper Website (Click Here) with your account. Remember to choose Image for Virtual Appliance.

2. In ESXi 5.5, Deploy OVA Template -> Choose downloaded ova file





3. Start Juniper JunOS Space in ESXi 5.5 and Complete basic configuration

3.1 User IDs

After you first time logged into Juniper Space with default account, you will be asked to change admin password right away.

There are three different user IDs for Juniper JunOS Space as follows:

  • admin user for CLI login  (default password: abc123)
  • super user for WebUI (default password: juniper123)
  • Maintenance user for maintenance operations. The password is set by the admin user during the initial configuration (that is, there is no default password).




3.2 Network Interfaces

By default, JunOS Space Virtual Appliance have four network interfaces:
  • eth0 -  SSH and device management if eth3 is not configured (node IP). But Secure Shell Daemon (sshd) is listening on all IP addresses.
    • eth0:0 - GUI interface with an instance of JBOSS running (GUI). The web GUI interface is only on the VIP, the same subnet as eth0.
  • eth1 - Not supported before Junos Space Network Management Platform Release 14.1R1. From 14.1R1 onwards you can configure the eth1 Ethernet interface as an administrative interface.
  • eth2 - Not supported
  • eth3 - Device management when managed devices are on a subnet and not reachable by way of eth0. Device management, outbound (discover) and inbound (post-discovery), including syslog and DMI, should be eth3, or eth0 if eth3 is not configured.

Configure Eth0:

Configure Eth3 for Device Management  and configure eth0.0 for Web GUI:

Configuration Summary:
Eth0: 192.168.2.70  Gateway: 192.168.2.1  DNS: 8.8.8.8
Eth3: 172.17.3.70
Eth0.0 : 192.168.2.72
Note: Eth0.0 IP Address has to be in same network as Eth0.

3.3 Apply Settings

 The following five screen shots are showing the system configuring process:


3.4 Web GUI 


3.5 SSH Session

SSH works on all Interfaces. Following output is SSH session on eth0 interface:



Last login: Tue Aug 18 15:55:47 2015

Welcome to the Junos Space network settings utility.

Initializing, please wait

Junos Space Settings Menu

1> Change Password
2> Change Network Settings
3> Change Time Options
4> Retrieve Logs
5> Security
6> Expand VM Drive Size
7> (Debug) run shell

A> Apply changes
Q> Quit
R> Redraw Menu

Choice [1-7,AQR]: 7

[sudo] password for admin: 
[root@space-005056920010 ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:56:92:00:10  
          inet addr:192.168.2.70  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fe92:10/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13408 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20862 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2127342 (2.0 MiB)  TX bytes:18231701 (17.3 MiB)

eth0:0    Link encap:Ethernet  HWaddr 00:50:56:92:00:10  
          inet addr:192.168.2.72  Bcast:192.168.2.255  Mask:255.255.255.0       
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth1      Link encap:Ethernet  HWaddr 00:50:56:92:00:11  
          inet6 addr: fe80::250:56ff:fe92:11/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1134 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:87488 (85.4 KiB)  TX bytes:758 (758.0 b)

eth2      Link encap:Ethernet  HWaddr 00:50:56:92:00:12  
          inet6 addr: fe80::250:56ff:fe92:12/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1100 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:85012 (83.0 KiB)  TX bytes:758 (758.0 b)

eth3      Link encap:Ethernet  HWaddr 00:50:56:92:00:13  
          inet6 addr: fe80::250:56ff:fe92:13/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1071 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:83708 (81.7 KiB)  TX bytes:758 (758.0 b)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3085894 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3085894 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2317104090 (2.1 GiB)  TX bytes:2317104090 (2.1 GiB)

4. Log into Web UI

Before you are able to successfully see JunOS Space log in window, you may see a progress bar presenting you the process starting:


Web GUI only works on eth0.0 interface, which is ip 192.168.2.72, not on 192.168.2.70, although they are on same network. Default username and password is 'super' and 'juniper123'.



Reference:

1. Deploying a Junos Space Virtual Appliance
2. Junos Space Virtual Appliance
3. Junos ® Space Virtual Appliance Deployment and Configuration Guide








Tuesday, May 5, 2015

Using Command Line to Do First Time Wizard on Checkpoint Appliance without WebUI

Three years ago, I got a problem to do first time configuration wizard at SPLAT platform using WebUI remotely because CheckPoint by default set mgmt interface ip to 192.168.1.1. I have no way to change this mgmt interface ip address  and has to use a special trick to touch some files to bypass the first time wizard requirement before I can type some other CheckPoint commands such as Sysconfig or CPCONFIG.

Basicall you will have to touch wizard_accepted file from expert mode based on Checkpoint KB 71000 First Time Configuration Wizard on Check Point appliances
  • SecurePlatform OS:
    touch /opt/spwm/conf/wizard_accepted
  • Gaia OS:
    touch /etc/.wizard_accepted
This year, I had a Gaia R76 4200 appliance installed at remote site. Console access is ready, and mgmt interface is connected to network. Unfortunately, it is pre-configed to 192.168.1.1 as well. I managed to configed it using my way to bring it up.

1. Steps to run first time wizard at Gaia using command line

1.1 Confirm CPCONFIG is not availabe without run First Time Wizard first. 

gw-379eb9> cpconfig
In order to configure your system, please access the Web UI and finish the First Time Wizard.

1.2 Set Up Expert Password

gw-379eb9> set expert-password 
gw-379eb9> expert
Enter expert password:

1.3 Touch the magic file

[Expert@gw-379eb9:0]# touch /etc/.wizard_accepted
[Expert@gw-379eb9:0]# exit
exit

1.4 Change Mgmt Interface IP Address for Remote WebUI Access

gw-379eb9> set interface Mgmt ipv4-address 10.9.2.15 mask-length 24
gw-379eb9> set static-route default nexthop gateway address 10.9.2.1 on
gw-379eb9> set static-route default nexthop gateway address 192.168.1.254 off
gw-379eb9> save config

1.5 CPCONFIG for CheckPoint Product Configuration

gw-379eb9> cpconfig


Welcome to Check Point Configuration Program
=================================================
Please read the following license agreement.
Hit 'ENTER' to continue...



Software License Agreement & Limited Hardware Warranty
Check Point Software Technologies Ltd.

PART I - SOFTWARE LICENSE AGREEMENT

This License Agreement (the "Agreement") is an agreement between you (both the i
ndividual installing the Product and any legal entity on whose behalf such indiv
idual is acting) (hereinafter "You" or "Your") and Check Point Software Technolo
gies Ltd. (hereinafter "Check Point").

TAKING ANY STEP TO SET-UP, USE OR INSTALL THE PRODUCT CONSTITUTES YOUR ASSENT TO
 AND ACCEPTANCE OF THIS AGREEMENT. WRITTEN APPROVAL IS NOT A PREREQUISITE TO THE
 VALIDITY OR ENFORCEABILITY OF THIS AGREEMENT AND NO SOLICITATION OF ANY SUCH WR
ITTEN APPROVAL BY OR ON BEHALF OF YOU SHALL BE CONSTRUED AS AN INFERENCE TO THE
.......


Select installation type:
-------------------------

(1) Stand Alone - install Check Point Security Gateway and Security Management.
(2) Distributed - install Check Point Security Gateway, Security Management and/or Log Server.

Enter your selection  (1-2/a-abort) [1]: 2


Select installation type:
-------------------------

(1) Check Point Security Gateway.
(2) Security Management.
(3) Security Management and Check Point Security Gateway.
(4) Enterprise Log Server.
(5) Check Point Security Gateway and Enterprise Log Server.

Enter your selection  (1-5/a-abort) [1]: 1
Is this a Dynamically Assigned IP Address gateway installation ? (y/n) [n] ? n
Would you like to install a Check Point clustering product (CPHA, CPLS or State Synchronization)? (y/n) [n] ? y
IP forwarding disabled
Hardening OS Security: IP forwarding will be disabled during boot.
Generating default filter
Default Filter installed
Hardening OS Security: Default Filter will be applied during boot.
This program will guide you through several steps where you
will define your Check Point products configuration.
At any later time, you can reconfigure these parameters by
running cpconfig



Configuring Licenses and contracts...
=====================================
Host             Expiration  Signature                             Features          

Contract Coverage:

There is no contract coverage for the above licenses.
Note: The recommended way of managing licenses is using SmartUpdate.
cpconfig can be used to manage local licenses only on this machine.

Do you want to add licenses (y/n) [y] ? n


Configuring Administrator...
============================
No Check Point products Administrator is currently
defined for this Security Management Server.

Do you want to add an administrator (y/n) [y] ? n


No administrator is currently defined.
Are you sure you want to continue? (y/n) [n] ? n

Do you want to add an administrator (y/n) [y] ? y
Administrator name: admin
Password:
Verify Password:

Administrator admin was added successfully and has
Read/Write Permission for all products with Permission to Manage Administrators


Configuring GUI Clients...
==========================
GUI Clients are trusted hosts from which
Administrators are allowed to log on to this Security Management Server.

No GUI Clients defined
Do you want to add a GUI Client (y/n) [y] ? n


Configuring Random Pool...
==========================
Automatically collecting random data to be used in
various cryptographic operations.
.....


After all basic configuration completed, the appliance will be rebooted then you will be able to access it through WebUI, SSH or connect it to Smart Dashboard.

2. Checkpoint KB 69701 :

Run First Time Wizard at Command line using config_system command:

Checkpoint offers another command config_system to do First Time Wizard using a template file. It seems more complicated way to do compare CPCONFIG's wizard way. 

  • [Expert@HostName]# config_system -t <file_name>

           This will create an empty template file for system configuration.

  • Open the file you created with a text editor and fill the appropriate fields.

  • [Expert@HostName]# config_system -f <file_name>

This will run the First Time Configuration Wizard with the information provided in the filename.



Reference:

1. First Time Configuration Wizard on Check Point appliances
2. How to run the First Time Configuration Wizard through CLI in Gaia