Security fundamentals

7 Types of Cybersecurity & the Five Cs Explained

A practical guide to seven security areas, the limits of five-Cs mnemonics, and how data protection fits into the NIST CSF 2.0 functions.

The short answer

A practical seven-area cybersecurity model covers network, endpoint, application, cloud, data, identity and operational security. This is a learning aid, not a universal standard. Formal frameworks organize outcomes differently; NIST CSF 2.0 uses six functions.

What are five types of cybersecurity and examples?

A shorter learning model can group the subject into network, endpoint, application, cloud and data security. A firewall rule illustrates network control; a managed laptop illustrates endpoint protection; an application permission check illustrates application security; cloud access configuration illustrates cloud security; and a sensitive-file sharing policy illustrates data security.

Five-area and seven-area lists are different ways of organizing a broad subject, not competing universal standards. Identity, staff practices, physical safeguards and operational processes remain important even when they are not separate entries in a short list. Use the categories to identify responsibilities and gaps in a real business workflow.

What are the seven types of security or cybersecurity?

Different courses and vendors count security domains differently. For a business technology discussion, the following seven areas provide a useful map. Physical controls and staff practices also matter across these areas; this list is not intended to exclude them.

  • Network security: limits and monitors communication between systems and environments.
  • Endpoint security: protects laptops, desktops and other supported devices.
  • Application security: addresses weaknesses in software design, configuration and operation.
  • Cloud security: manages risks in cloud services and their shared responsibilities.
  • Data security: protects information through access controls, classification, appropriate encryption and DLP.
  • Identity security: governs accounts, authentication, authorization and privileged access.
  • Operational security: covers monitoring, change processes, staff practices, incident handling and continuity.

Where does DLP fit into these areas?

DLP belongs primarily to data security, but it can enforce policy through an endpoint, email workflow, cloud integration or network control. This is why buying products by domain label can be confusing. One product may touch several domains while still leaving gaps in a specific workflow.

Take an employee sending a sensitive attachment. Identity establishes the account and permissions; email infrastructure delivers the message; a DLP control may inspect the proposed disclosure; monitoring records the decision. Ownership and response procedures determine what happens after an alert.

What are the five Cs of cybersecurity?

There is no single universally adopted five-Cs standard. An article or course may use that phrase for its own mnemonic. Always check the definitions instead of assuming two lists mean the same thing.

For an internal planning exercise, a team could use confidentiality, control, continuity, compliance and culture as prompts: what must remain private, who can do what, how operations recover, which obligations apply, and how people work safely. This is our explanatory mnemonic, not a NIST or ISO taxonomy, and it should not replace a formal risk assessment.

Does NIST use five or six cybersecurity functions?

NIST CSF 2.0 uses Govern, Identify, Protect, Detect, Respond and Recover. Older CSF 1.1 material often refers to five functions because Govern was added in version 2.0. Use the framework version and actual outcomes when mapping controls rather than mixing an older list with a newer programme.

References: NIST: Cybersecurity Framework 2.0 and its six functions

How can a business turn these categories into a plan?

Choose an important business process and map its information, users, devices, applications and external dependencies. Identify a small number of realistic failure or disclosure scenarios, then agree preventive, detective and recovery responsibilities. A domain checklist becomes useful only when it leads to decisions and testing.

For a DLP pilot, document the sensitive data, approved sharing routes, restricted destinations, policy owner and evidence required after an event. Review access and privacy implications alongside technical controls. Test the result periodically and after material workflow changes.

Put the answers to work

Test the controls on your own data paths.

Use synthetic data and a written checklist to compare outcomes. Explore our pricing, read the buyer guide or book a product walkthrough with your requirements.

About this guide

Published by Sentrix Axis, a DLP software vendor. Product capabilities, leadership and licensing can change; check the linked official sources and current proposal. Vendor shortlists are editorial examples, not independent rankings. Career articles do not represent a salary survey.

Continue reading

Related questions, answered.