JN0-336 tests SSL proxy with two listed items, certificates and client and server protection, plus a line that asks you to configure, monitor or troubleshoot it on an SRX Series firewall. In practice that means one skill above all: telling a forward proxy (client protection) from a reverse proxy (server protection) and knowing which certificate each one needs.
SSL proxy is the smallest of the seven JNCIS-SEC objective areas on paper, and that is exactly why it gets skipped. Most JN0-336 study notes spend pages on IPsec VPN and chassis clusters and give SSL proxy one sentence. This post goes the other way. It takes the SSL proxy objective apart, links each idea to the Junos configuration it maps to, and then places it in a six-week plan for the whole exam. Every exam fact here was checked on HPE Juniper Networking's own pages on 19 November 2026.
What is the JN0-336 exam?
JN0-336 is the written exam for Security, Specialist (JNCIS-SEC), the second step of the HPE Juniper Networking security track. The track runs JNCIA-SEC, JNCIS-SEC, JNCIP-SEC and JNCIE-SEC, and this exam is aimed at engineers with intermediate knowledge of Junos OS on SRX Series devices.
These are the facts from the JNCIS-SEC certification overview on the Juniper Learning Portal:
- Exam code: JN0-336
- Prerequisite: JNCIA-SEC
- Format: 65 multiple-choice questions
- Time: 90 minutes, about 83 seconds per question
- Software version: Junos OS 24.4
- Language: English only, with pass or fail shown right after the exam
- Validity: three years
- Recommended course: Juniper Security
- Price: the JNCIS/JNCDS exam voucher is US$300 in Pearson VUE's US voucher store
Juniper publishes no passing score and no weight per objective. If a site tells you SSL proxy is a fixed share of the exam, that number did not come from the official page. Plan by the objective list instead.
Where does SSL proxy sit among the JN0-336 objectives?
SSL proxy is one of seven objective areas. Here is the full list as the portal shows it today:
- Intrusion Detection and Prevention (IDP)
- IPsec VPN, including Juniper Secure Connect
- Juniper Advanced Threat Prevention (ATP) Cloud
- High Availability (HA) clustering
- Identity-aware security policies (JIMS)
- SSL proxy
- Junos Space Security Director
The SSL proxy objective has two lines. The first asks you to identify the concepts, general features or functionality of SSL proxy, and it names two items: certificates and client and server protection. The second asks you to demonstrate how to configure, monitor or troubleshoot SSL proxy.
Notice that Security Director, the last area, has no configure line. SSL proxy does. So expect questions that show you a profile or a statistics output and ask what it does, not only questions about definitions.
What do client protection and server protection mean on an SRX?
Client protection is the forward proxy and server protection is the reverse proxy. Both decrypt traffic so the SRX can inspect it, but they face in opposite directions.
An SSL proxy on an SRX is transparent. To the client it acts as the server, and to the server it acts as the client. Juniper's documentation describes the two types like this:
- Client protection (forward proxy): the SRX sits between your internal users and servers on the internet. It handles outbound sessions, decrypts what your users send and receive, and inspects it.
- Server protection (reverse proxy): the SRX sits between your own server and clients on the internet. It handles inbound sessions that start outside and end on your server.
A simple way to remember it: forward proxy protects your people, reverse proxy protects your servers. If an exam scenario describes staff browsing the web, think forward. If it describes a public web server in a DMZ, think reverse.
Which certificate does each type of SSL proxy need?
This is the certificates item of the objective, and it is the cleanest rule to memorise. A forward proxy profile needs a root CA certificate. A reverse proxy profile needs the server's own certificate and private key.
The HPE Networking guide to configuring SSL forward and reverse proxy gives a small table that decides the profile type:
- root-ca only: the profile is a forward proxy
- server-certificate only: the profile is a reverse proxy
- neither: commit check fails
- both in one profile: commit check fails
Two more points follow from that table. First, a single firewall policy can use only one profile, either forward or reverse. Second, one device can still run both kinds at once on different policies.
What the client sees is different too. With a forward proxy, the SRX generates a new certificate for each site, signed by your root CA, so client machines must trust that CA. With a reverse proxy, the SRX passes the real server certificate chain to the client unchanged. Juniper's documentation says it directly: intercepting the server certificate happens only with forward proxy.
What happens when the server's certificate fails a check?
By default, if the SRX cannot authenticate the real server, the connection is dropped. An option called ignore-server-auth-failure changes that. With it, the SRX still builds a certificate, but in a way that makes the user's browser show a warning. Juniper does not recommend this option for normal use, because servers are then not authenticated at all. It is meant for finding out why sessions are being dropped.
Certificate revocation checking is also on by default in SSL proxy profiles. You can turn it off, or choose to allow or drop sessions when revocation information is missing.
How do you configure a basic forward proxy?
The minimum forward proxy has two parts: an SSL proxy profile, and a security policy that calls that profile as an application service. In Juniper's own example, the profile names the root CA with root-ca, trusts all CAs with trusted-ca all, and is then attached to a trust-to-untrust policy that permits HTTPS traffic.
The detail that matters for the exam is where SSL proxy lives. It is not a separate rule base. It is an application service inside an ordinary security policy, the same place where you call IDP or other services. A reverse proxy works the same way, except the profile points to a server certificate that you first load into the PKI store with its key.
Why does an SSL proxy profile sometimes do nothing at all?
Because SSL proxy only runs when there is a reason to decrypt. If no service that uses the decrypted traffic is active on the session, the SRX bypasses SSL proxy, even though the profile is attached to the policy.
The services that use decrypted traffic include IDP, application firewall, application tracking, advanced policy-based routing, Content Security, ATP Cloud and ICAP redirect. This is one of the most useful facts to carry into the exam. A scenario that says "the profile is configured but sessions are not decrypted" often points here.
Two related behaviours are worth knowing:
- SSL proxy uses application identification to decide whether a session is really SSL. Sessions that are not SSL are ignored.
- If IDP SSL inspection and SSL proxy are both enabled on one session, SSL proxy wins. Juniper now recommends SSL reverse proxy with IDP instead of the older IDP SSL inspection, which is deprecated.
Which sessions does SSL proxy drop?
The Junos documentation lists clear limits, and they make good troubleshooting material:
- SSLv2 sessions are dropped, and SSLv3 is deprecated.
- Only X.509v3 certificates are supported.
- Client authentication is not supported, so sessions where the server requires a client certificate are dropped.
- Sessions that ask for renegotiation are dropped.
- SSL proxy is not supported on SRX firewalls in a Multinode High Availability setup.
On the protocol side, SSL proxy supports TLS 1.2 and TLS 1.3, and recent releases deprecate TLS 1.0 and 1.1 for SSL proxy.
How do you check that SSL proxy is working?
Start with the operational command show services ssl proxy statistics. It shows counters such as sessions matched, sessions created, sessions ignored, sessions dropped and sessions bypassed because they were not SSL.
Here is a scenario of the kind the troubleshooting line points to, written for this post. A team builds a forward proxy profile with a root CA, attaches it to the trust-to-untrust policy for HTTPS, and commits without errors. Users browse normally, but the security team sees no application details in its logs, and the statistics show sessions matched while none are created.
Work through it the way the objective expects. The profile is valid, because it has root-ca and no server-certificate. The policy calls it. So ask what would use the decrypted data. If no IDP policy, application firewall, AppTrack or other service is active on that policy, the SRX has no reason to decrypt, and it bypasses SSL proxy. Turning on the service the team actually wants, such as application tracking, is the fix. The certificates and the profile were never the problem.
How does SSL proxy connect to the other JN0-336 objectives?
SSL proxy feeds the rest of the exam. IDP needs decrypted traffic to see attacks inside HTTPS. ATP Cloud can use decrypted content too. That is why learning SSL proxy late in your plan is a mistake: it explains behaviour in two other objective areas.
Decryption is also not a Juniper-only topic. If you work in a mixed estate, the same idea appears in Palo Alto's blueprint, which our earlier notes on the NetSec-Pro exam domains cover from that vendor's side.
Is there a short video overview of JN0-336?
Yes. This short NWExam video gives an overview of the JN0-336 exam and how to plan your study. Use it for orientation, then come back to the official objectives for the details.
What should you know before starting JNCIS-SEC?
The formal prerequisite is JNCIA-SEC. Beyond that, you need to be comfortable with the Junos CLI itself: the configuration hierarchy, commit and rollback, and reading show output quickly. Every SSL proxy step in this post is Junos configuration, so weak CLI habits cost time in a 90-minute exam. If that foundation still feels shaky, our post on the JNCIA-Junos JN0-106 exam as the entry point to Junos covers it.
What does a six-week JN0-336 study plan look like?
Six weeks at about six to eight hours a week works for most engineers who already passed JNCIA-SEC. Adjust it to your own lab access.
- Week 1: Read the seven objectives line by line. Set up a lab SRX (physical or virtual) and practise zones, policies and commit habits.
- Week 2: IPsec VPN: tunnel establishment, traffic processing, site-to-site VPNs and Juniper Secure Connect. Build one tunnel and break it on purpose.
- Week 3: SSL proxy, then IDP. Build a forward proxy, read the statistics, then add an IDP policy and watch the counters change.
- Week 4: ATP Cloud and identity-aware policies. Focus on components, workflow and how JIMS feeds user identity to policies.
- Week 5: HA clustering: chassis cluster operation, deployment requirements and state synchronisation. Then Security Director concepts.
- Week 6: Review weak areas with official resources and timed reading of show output. Aim for about 80 seconds per question.
Putting SSL proxy before IDP in week 3 is deliberate. Once decryption works, the IDP and ATP Cloud material makes more sense. The same objective-by-objective method works for other Junos exams too; our JN0-650 EVPN objectives breakdown applies it to a professional-level blueprint.
What mistakes do candidates make on the SSL proxy objective?
- Mixing up the directions. Client protection is forward, server protection is reverse. Say it out loud until it is automatic.
- Putting both certificates in one profile. root-ca and server-certificate together fail the commit check.
- Forgetting the client side of forward proxy. Users must trust the root CA, or every site shows a warning.
- Expecting decryption without a service. No IDP, AppFW, AppTrack or similar service means SSL proxy is bypassed.
- Leaving ignore-server-auth-failure on. It is a troubleshooting aid, not a normal setting.
- Trusting unofficial weights. No official weight exists for any JN0-336 objective.
How should you register and what does it cost?
You schedule JN0-336 through Pearson VUE. The Pearson VUE page for Juniper Networks exams notes that the program is now called the HPE Networking Certification Program, and that sign-in to Alpine CertMetrics moved to an hpe.com username from 15 September 2026.
The JNCIS voucher costs US$300 in the US voucher store, so it pays to sit the exam once you are ready rather than as a trial run.
Once the SSL proxy material is solid, the next step is checking your timing across all seven areas. The JN0-336 practice exam for JNCIS-SEC on NWExam covers the whole blueprint in timed sessions.
Frequently asked questions
1. How many questions are on the JN0-336 exam?
JN0-336 has 65 multiple-choice questions and a time limit of 90 minutes, according to the Juniper Learning Portal. It is based on Junos OS 24.4 and is offered in English only.
2. What is the difference between forward and reverse SSL proxy on an SRX?
Forward proxy (client protection) decrypts outbound sessions from internal users to the internet and needs a root CA certificate. Reverse proxy (server protection) decrypts inbound sessions to your own server and needs that server's certificate and private key.
3. Why is my SSL proxy profile not decrypting traffic?
The SRX bypasses SSL proxy when no service uses the decrypted traffic. Turn on a service such as IDP, application firewall or application tracking on the same policy, and confirm the session is really SSL.
4. What is the prerequisite for JNCIS-SEC?
The prerequisite certification for JNCIS-SEC is JNCIA-SEC. Juniper certifications stay valid for three years.
5. What is the passing score for JN0-336?
Juniper does not publish a passing score for JN0-336, and it publishes no weight for each objective area. Pass or fail is shown right after the exam.

