Chapter 8 · Reading 2 of 5
Placing controls at trust boundaries
Security+ SY0-801 · Objectives 3.2, 4.1
Visitors use the college’s wireless network in the same building where advisors review confidential records. Sharing a building is convenient. Sharing unrestricted paths between guest devices and the advising service creates a very different relationship. Where would you draw the boundary without preventing visitors from using legitimate services?
A zone groups systems with similar trust and communication requirements. Document each permitted flow with its source, destination, protocol and business purpose. Place a firewall where it can enforce the boundary. A passive sensor observes mirrored traffic, while an inline prevention device can interrupt traffic and introduces a failure-mode decision. Consider both service availability and exposure when designing a bypass.
Enforce access at admission
Use network access control to evaluate device or user posture at admission. Enforce application authorization after admission. Segregate management interfaces and provide a controlled administration path. Industrial devices may need passive monitoring and a scheduled change window because a restart affects physical operations. Validate segmentation with approved connectivity checks and review logs for legitimate traffic disrupted by a policy.
Begin with the transaction that should work
A guest device needs a network address, approved name resolution and access to intended public services. An advisor’s managed device may also need a private appointment service. An administrator needs a controlled maintenance path. Write the required flows in plain language before translating them into rules. Include return traffic, service dependencies and the person who can confirm each purpose. A vague exception for a whole department can survive long after the original dependency has disappeared.
Compare observation and enforcement. A passive sensor outside the advising zone can report a connection while allowing it to proceed. An inline control can reject it but becomes a dependency for legitimate traffic. Decide what happens during maintenance and what evidence is retained when the control itself fails. A network allowing a connection still leaves the application responsible for deciding which record the user may read.
A rule review a service owner can read
Consider a proposal allowing all managed devices to reach the advising database because staff use the advising application. Follow a normal transaction. The advisor's browser contacts the application. The application, under a service identity, contacts the database. An allowance for every staff laptop to reach the database would introduce a path that this transaction never uses. Ask the owner to identify any separate administrative requirement and document that flow separately.
Now consider an after-hours support call. If support normally enters through an approved management service, create a test for that path and its authorization. A configuration that blocks legitimate recovery may encourage improvised exceptions during an outage. Store the allowed transaction, denied transaction and support procedure with the drawing. The next reviewer can then evaluate proposed changes in terms of actual users and dependencies.
Test the drawing against the service
Use approved test identities and synthetic records. Confirm a guest can resolve names and reach the public site, an advisor can use the appointment service and the guest cannot reach its private management interface. Save the observed results with the rule and change owner. A boundary diagram that correctly predicts those outcomes is a useful tool for the next question: what will the service do when one of those dependencies is lost?
Inspect the three records, then use the evidence to answer the question.
1. Record A
Guest clients require DNS through resolver R1
2. Record B
Payroll application runs on a separate segment
3. Record C
Gateway currently permits guest access to both
Apply the reading
What evidence supports your decision in the network policy drawing exercise?
Compare your reasoning
Permit the documented DNS dependency and remove the unrelated path. Verify both name resolution and the payroll boundary after the change.