AA - General Review FSA Topics Flashcards
Policy, sub rules. bit of NAC, Groups, Conditions
Centralized Deployment
Single site architecture - remote sites managed via centralized appliances - Deployed as Layer 3>> No span traffic to remote site Issues: Bandwidth concerns - number of managed switches at remote sites - Microsoft vulnerability compliance
Hybrid Deployment
Sites with appliances and sites without appliances Crucial or strategic sites have appliances - Smaller less critical sites, no appliance> but bandwidth concerns
Distributed Deployment
- Overall best solution
- Multiple Site appliances
- One to one mapping of site to appliance
- Enhanced IPS and HTTP redirect actions
- utilizes layer 2 (this layer can do threat protection)
- Less bandwidth
Location of Appliances
SPAN = Better visibility!
- Place where most valuable traffic can be monitored:
>Internet Access Points (IAP) - Required for consistent HTTP notifications
> Auth and DHCP Traffic - used to clarify unmanageable/unknown endpoints based on activity
> core switches/datacenterd/sesitive zones
- Traffic that should not be monitored
> BAckup Networks (if segregated)
> Encrypted traffic (tunnels)
Channel Configuration

High Availability - Single Switch
You need visibility into both switches !!!!!

High Availability - Redundant Switch Connectivity

Quiz - FSA Refresh

Initial Discovery
- Packet Engine parses and analyzes mirrored data
> Builds a real-time contextual database - host profile
> MAC address/IP address
> Default discovery policy (Options>Discovery) defines the rules that instruct the appliance on properties to collect even before policy is enables
- Also uses NMAP, DNS and DHCP for additional host properties
- Policies then use the hostp profile information to
> determine device type - what is it
> Whose is it? - Is it a corporate device or guest? BYOD?
> Is it safe to be on the internal network
> control access
Policy Irresolvable
Irresolvable: Means host does not meet conditions. Question cannot answer.
Irresolvable: This is our bitbucket for devices that we could not identify clearly. So we can take time workin through them.

Policy Folders
- See
- 1 Discover
- 2 Classify
- 3 Asses
- 0 Control
- 0 Orchestrate
- 0 Informational
- 0 Policy Rollout Testing
Policy Flow - Groups
Ignored IPs: Devices will be still discovered but thei are not going through a policy evalauation
Passive- Learning: Not actively scanning nmap or credentialed scan
Tenable Scanner:In CounterACT you have to do Threat Protection Exemption!!! It’s the first thing that we did as the first thing in the FSCA class. >> Add it to Legitimate Scan. Counteract creates kind or a reactive honeypot. This is why it creates the ghost devices for Maybe the way switches are queried or admission events for go

Discover Policy
- Questions
- Conditions

Classify Policy
This is where we can look at network devices and printers. What community strings are they using.
Or we break down mobile devices.

Assessment Policy
Think about the logic process. If you already have an answer from the first rule do not ask the question again.

Control Policy

Quiz 2 - FSA Review

Quiz 3 - FSA REview

NAC - Connection LIfecycle and Access Control Enforcement
ForeSCout NAC:

Instead of (just) 802.1x ForeScout uses: MAR – MAC … Repository. Is more dynamic in nature
NAC Pre-Connect Connection LifeCycle Flow
Both the Pre and Post Connect Paradigms are valid approaches to network access control.
> Depending on which is chosen, the specific policy configuration will vary
> Restrictive Control actions will be taken at different point in the policy set
The NAC paradigm should be decided upon prior to policy creation.

Post-Connect Connection Lifecycle Flow
Both the Pre and Post Connect Paradigms are valid approaches to network access control.
> Depending on which is chosen, the specific policy configuration will vary
> Restrictive Control actions will be taken at different point in the policy set
The NAC paradigm should be decided upon prior to policy creation.
