secplus

Dashboard / 3.0 Security Architecture

3.3 Compare and contrast concepts and strategies to protect data

Official exam objective outline (4 topics)
  • Data types
    • Regulated
    • Trade secret
    • Intellectual property
    • Legal information
    • Financial information
    • Human- and non-human-readable
  • Data classifications
    • Sensitive
    • Confidential
    • Public
    • Restricted
    • Private
    • Critical
  • General data considerations
    • Data states: Data at rest, Data in transit, Data in use
    • Data sovereignty
    • Geolocation
  • Methods to secure data
    • Geographic restrictions
    • Encryption
    • Hashing
    • Masking
    • Tokenization
    • Obfuscation
    • Segmentation
    • Permission restrictions

★ Starred in your notes: full-disk encryption = laptops/disks; full-device encryption = mobile.

Breakdown 1 — Data types and classifications

Data typeExampleWhy it's special
RegulatedPHI (HIPAA), cardholder data (PCI DSS), EU personal data (GDPR)Law dictates controls, breach notification, fines
Trade secretFormulas, algorithms, customer listsLoses protection if disclosed
Intellectual propertyCopyright (DRM), patents (class)Legal ownership; DRM controls copying
Legal informationContracts, litigationPrivileged, retention rules
Financial informationStatements, card numbers, payrollSOX/GLBA/PCI
Human- vs. non-human-readableDocuments vs. binary/encrypted/machine dataNon-human-readable still needs classification

Classifications (labels): Public · Private · Sensitive · Confidential · Restricted · Critical. Government style: Unclassified → Confidential → Secret → Top Secret. The label drives the handling rules (encryption, who may access, retention).

Breakdown 2 — Data states (class: "in motion, at rest, in use — in RAM")

StateWhereProtect with
At restDisk, database, backup tapeFDE/SED, file/database encryption, access control
In transit / in motionOn the networkTLS, IPsec, SSH, VPN
In useRAM/CPUMemory encryption, secure enclave, homomorphic encryption; cold boot attack extracts keys from RAM (class)

Sovereignty and geolocation: Data sovereignty = data is subject to the laws of the country where it is stored (GDPR is the classic example). Geolocation = knowing/controlling where data physically lives; geographic restrictions (geofencing) block access or storage outside approved regions.

From class — the information life cycle: creation/acquisition → use/storage → retention/archival → wiping/disposal. Controls apply at every stage; disposal = sanitization/destruction (4.2).

Breakdown 3 — Methods to secure data

MethodWhat it doesReversible?
EncryptionScrambles with a keyYes, with the key
HashingOne-way fingerprint for integrity/password storageNo
MaskingShows only part (****1234) or substitutes fake values for display/testingNo (displayed copy)
TokenizationReplaces value with a random token; real value in a vaultOnly via the vault
ObfuscationMakes data hard to interpret (including steganography)Varies
SegmentationKeep sensitive data on its own network/storage zone—
Permission restrictionsLeast privilege, NTFS/share ACLs (most restrictive wins)—
Geographic restrictionsOnly from/in approved regions—

From class — privacy-enhancing technologies: anonymization (remove identifying data permanently), pseudo-anonymization (replace identifiers with pseudonyms; re-identifiable with a key), tokenization, data scrubbing/minimization. DLP — data loss prevention (e.g., blocking uploads to social media, stopping card numbers in email). DRM — digital rights management (copyright enforcement). Data segmentation.

From class — encryption at the device level: Full-disk encryption → laptops/disks; full-device encryption → mobile phones (if the question says "mobile"). Disk encryption options: stacked file system encryption, block-device encryption, self-encrypting drive (SED), secure enclave. Windows: EFS (per file/folder), BitLocker (whole drive, TPM-backed).

Breakdown 4 — Exam scenarios

ScenarioBest answer
Developers need realistic test data without real customer infoMasking (or anonymization)
Reduce PCI scope for stored card numbersTokenization
Data must stay in the EUData sovereignty / geographic restriction
Prevent employees emailing spreadsheets of SSNsDLP
Laptop stolen while offFDE
Sensitive data processed in the cloud without exposing it in memorySecure enclave / homomorphic encryption
Analytics on personal data while limiting re-identificationPseudonymization

Quick self-check

  • Three states of data and one control for each. (At rest/FDE; in transit/TLS; in use/enclave.)
  • Tokenization vs. masking? (Token reversible via vault; mask is display-only.)
  • What does "data sovereignty" mean? (Local law applies where the data sits.)

Sources: 20260917_182454.jpg, 20260917_182502.jpg, 20260917_182510.jpg