Barracuda CloudGen Firewall Administration · Firewall administration

Architecture, deployment models, first setup and management

Architecture, deployment models, first setup and management. Reading chapters, hands-on simulator labs, interview questions, scenarios and a quiz.

44 min read8 chapters2 labs12 quiz6 scenarios12 interview Q&A

This first module is free: read the lesson and take the quiz. Labs need an account: sign up free to run up to 3 hands-on labs.

Log inStart free trial
This reading material cannot be printed. Read it on config.nwkings.com.
01

What you will learn: the CloudGen firewall in context

What you will learn

This track teaches how a next-generation firewall built around central management, secure tunnels and cloud deployment is designed, built and run. In this first module you meet the architecture and set up a first device. By the end you can:

  • explain what a next-generation firewall adds to a traditional one;
  • describe the box, service and central layers and what runs where;
  • choose between hardware, virtual and public cloud deployment;
  • complete a first setup: management access, interfaces, licence and updates;
  • confirm that a first rule allows safe traffic and that it appears in the logs.

Prerequisites: basic IP addressing, routing and the idea of zones. This is independent training in original wording, not made or endorsed by Barracuda.

Analogy: a security company with branches

Think of a security company with a head office and many branch offices. Each branch has guards who work alone every day, but head office sets the rules, sends updates and watches all branches. A CloudGen firewall is like that: each device can run alone, yet the design expects many devices and one central place to manage them.

Traditional versus next-generation

QuestionTraditional firewallNext-generation firewall
What does it see?Addresses and portsApplications, users, content and files
How does it decide?Is this port allowed?Is this application allowed, for this user, safely?
Extra protectionOften a separate boxBuilt in: intrusion prevention, malware scanning, filtering
BranchesConfigured one by oneCentral templates and policy
CloudHardware onlySame product in public cloud

Where this firewall is used

  • Head offices and data centres that need strong inspection.
  • Many small branch sites with a shared design.
  • Manufacturing and retail with many remote locations.
  • Public cloud networks that need the same policy as on-premises.

Why learn it

The ideas travel: zones, rules, tunnels, central control and logging appear in every vendor. Learning one design deeply makes the next product easier.

Branch devicesSecure tunnelsCentral managerLogs and reports

Many devices, one policy and one view.

A retailer has 60 shops. Each shop has a small firewall that connects to head office through an encrypted tunnel. A policy change is made once in the central manager and applied to every shop that night. Without central management an engineer would have to log in to 60 devices.

Common mistake: treating the firewall as a box that is configured once and forgotten. The strength of this design is that policy, updates and monitoring are managed continuously and centrally.

The shop that was different

One shop had a rule that others did not. It was added years ago for a printer and never removed. A central review showed the exception, and it was replaced by a template-controlled rule.

Lesson: central policy removes forgotten exceptions.

What does a next-generation firewall add?

It adds visibility and control over applications, users and content, plus built-in protection such as intrusion prevention and malware scanning, instead of deciding only on addresses and ports.

Key takeaways

  • Next-generation firewalls decide on applications, users and content.
  • The design expects many devices and central management.
  • The same product runs on hardware, virtual and cloud.
  • Concepts learned here carry across vendors.
  • Policy should be managed continuously, not once.

Upgrade to keep reading

The free plan lets you read chapter 1 of this module. Upgrade to open the remaining chapters.

  1. Architecture: box layer, services and central management
  2. Deployment models: hardware, virtual and public cloud
  3. First setup: management access and basic settings
  4. Interfaces, routing and the first traffic path
  5. Licences, subscriptions and keeping protection current
  6. Your first access rule and how to verify it
  7. Module summary and go-live checklist

Join the community