What is capacity planning?
Capacity planning is the ongoing work of making sure an organization has enough resources to meet demand, both on a normal busy day and during a recovery. It measures how much of each resource is used now, forecasts how that will change, compares the forecast with hard limits, and schedules purchases, hiring or contracts early enough that they arrive before the limit is reached. In security architecture it is usually split into three areas: people, technology and infrastructure.
People
Staff are a resource that disasters hit too. A regional storm that floods a data center also closes roads and schools for the people meant to restore it. If only one engineer knows how to rebuild the identity servers, that person is a single point of failure. Cross-training, written runbooks, on-call rotations, succession plans and incident response retainers add people capacity. The same thinking applies to a security operations center: if alert volume doubles during an incident, the team needs a plan for who triages the overflow.
Technology
Technology capacity covers compute, storage, software licenses, bandwidth and application limits. Recovery scenarios expose gaps that normal days hide. Restoring 12 TB of backups over a 1 Gbps link takes about 27 hours even at full line rate, so a 12-hour recovery target for that data can't be met without more bandwidth or a different restore method. A recovery site sized for half the normal load, or licenses tied to hardware at the primary site, are similar traps. Log capacity matters for security: a SIEM licensed for a fixed daily ingest, or a log server whose disk fills up, can drop events during the very incident that needs them.
Infrastructure
Infrastructure means power, cooling, rack space, network circuits and buildings at both the primary and recovery sites. Adding a row of servers without adding cooling, or relying on a generator with 24 hours of fuel during a three-day outage, are infrastructure capacity failures.
Example: a storage forecast
A log archive holds 100 TB, 64 TB of it is in use, and usage grows by about 3 TB a month. The team treats 80 percent full, 80 TB, as the point where performance and headroom become a problem, which arrives in a little over five months. With a three-month lead time for new storage, the order needs to go in within two months. Trend arithmetic like this, reviewed regularly, is most of capacity planning.
Capacity planning on the CompTIA Security+ exam
Capacity planning falls under SY0-801 objective 3.4, which covers resilience and recovery; expect it to be divided into people, technology and infrastructure. Wording such as "make sure enough trained staff are available during a disaster", "the recovery site can't handle the full production load" or "forecast resource needs for growth" points to capacity planning. Distractors include a business impact analysis, which identifies critical functions and the harm of losing them; autoscaling, which reacts to demand in the moment but still needs planned limits; load balancing; and a tabletop exercise.