Security+: Technologies and Tools – Proxy


The Security+ syllabus is updated every three years. Normally, the exam is denoted by a code consisting of a sequence of letters and numbers; for example, SY0-401 is the most recently outdated exam. During the revision, many changes have been made from the previous version to the most recent exam. This article covers the most recent changes leading to the current exam, the SY0-501. We will cover the changes related to proxies. We will look at how they were covered and how they are now covered, while also mentioning what candidates must know for the exam.

Exam Changes Overview

Between the two exams, SY0-401 and SY0-501, there is a significant overall change in the content. The new exam focuses on attacks, risk management, and hands-on skills using technologies and tools. As a result, the domains have been re-named and re-ordered to reflect cybersecurity trends as determined in the Security+ SY0-501 Job Task Analysis (JTA).

AWS Builder Community Hub

Under the previous exam (SY0-401), proxies were covered in the Network Security domain, specifically under section 1.1 Implement security configuration parameters on network devices and other technologies, which covered 20% of the overall exam, but is now currently found in the Technologies and Tools domain (22% of the overall exam) under section 2.2 Install and configure network components, both hardware and software-based, to support organizational security.

Compared to the previous exam, the most recent changes ensure that candidates are able to explain the concepts by translating them to real-life problems. This has been achieved by a 21% increase from the previous exam.

Exam Changes Comparison

There are various malicious motives for targeting organizations. They may include competitor companies that are out to obtain intellectual property from rival organizations (or execute espionage missions), rogue states that might sponsor attacks against certain industries that (Read more...)

*** This is a Security Bloggers Network syndicated blog from InfoSec Resources authored by Lester Obbayi. Read the original post at: