Attack surface
An attack surface is the set of exposed or reachable interfaces, components, capabilities, and pathways through which an attacker could access or affect a system.
100 SQL Server Mistakes and How to Avoid Them
An attack surface is the collection of system components and exposed capabilities that could be targeted to compromise a system.
- How it is used
- Guides SQL Server installation choices by exposing how unnecessary components, services, and features increase security exposure.
- How deep it goes
- Explains operational causes and consequences of exposure, but stops short of formal threat modeling or vulnerability assessment.
- Examples
- Uses Windows Server 2022, SQL Server 2022, SSIS, Visual Studio, and optional SQL Server services as concrete cases.
- What you can do after
- Operate/configure SQL Server installations by choosing Server Core where suitable and excluding unneeded features and services.
Read how 100 SQL Server Mistakes and How to Avoid Them explains attack surface →
Secure APIs
An attack surface is the collection of exposed interfaces, components, and entry points through which an attacker may affect a system.
- How it is used
- Manages exposed API entry points and infrastructure to reduce opportunities for abuse, unauthorized access, and sensitive-data exposure.
- How deep it goes
- Explains endpoints, versions, devices, and infrastructure, then reaches gateways, WAFs, and network restrictions without treating them as complete protection.
- Examples
- Uses mortgage workflows, a laundry-service API, vulnerable IoT devices, old API versions, and internal endpoints as concrete exposure examples.
- What you can do after
- Operate/configure API exposure by inventorying entry points, restricting infrastructure, and applying gateway, WAF, and access-control measures.
Think Like a CTO
The complete set of points, interfaces, systems, and pathways through which an attacker could compromise or leak organizational assets.
- How it is used
- Guides CTOs in identifying, reducing, monitoring, and repeatedly reassessing organizational exposure.
- How deep it goes
- Defines the concept and gives practical network and credential examples, while stopping short of exhaustive security treatment.
- Examples
- Uses shared database credentials, mixed production and development networks, network-connected devices, and newly deployed services.
- What you can do after
- Apply it by inventorying exposure, isolating environments, assigning accountable access, and reassessing defenses after changes.
Data Pipelines with Apache Airflow, Second Edition
An attack surface is the collection of possible points through which an attacker could attempt to gain unauthorized access to a system.
- How it is used
- Guides Airflow security decisions by identifying exposed components and reducing the paths available to attackers.
- How deep it goes
- Explains architecture-level exposure and demonstrates network, encryption, secrets-management, and update controls without exhaustively modeling every breach path.
- Examples
- Uses the Airflow UI, database, external IPs, allowlists, Fernet keys, and Vault-backed connections as concrete security examples.
- What you can do after
- Operate/configure Airflow with restricted service exposure, encrypted stored secrets, centralized credentials, and current security fixes.
Read how Data Pipelines with Apache Airflow, Second Edition explains attack surface →
Related concepts
- deployment pipelineproduced by · A sequence of automated or manual stages that builds, tests or validates, packages, and delivers software or models toward deployment.
- digital twinproduced by · A digital twin is a computational representation of a physical entity, process, or system that models relevant characteristics, state, or behavior.
- security hardeningaddressed by · Security hardening is the practice of reducing a system’s vulnerabilities and attack surface through secure configuration, protective controls, and removal of unnecessary functionality.
- dependencyproduced by · A software dependency is a component, resource, or prerequisite on which another software component or operation relies to function or proceed.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.