eAIS flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Risk treatment options

Mitigate, transfer, avoid, or accept. Residual risk after treatment must be documented and formally accepted by an accountable executive with defined thresholds.

Residual risk

The risk remaining after controls are applied. It is calculated and recorded in the risk register, then compared against the organization's risk appetite for formal sign-off.

ISO/IEC 27001

International standard specifying requirements for an information security management system (ISMS), including risk assessment, treatment, and continual improvement through the Plan-Do-Check-Act cycle.

Segregation of duties

Control ensuring no single person can both authorize and execute a sensitive action, such as approving and implementing access changes, reducing fraud and error risk.

GDPR special category data

Health data is special category under Article 9, requiring an additional lawful condition beyond Article 6, such as explicit consent or provision of health care.

HIPAA Safe Harbor

De-identification method removing 18 specified identifier categories, including names, dates, geographic details smaller than state, and device identifiers, so data is no longer protected health information.

GDPR breach notification

Controllers must notify the supervisory authority within 72 hours of becoming aware of a personal data breach, unless unlikely to result in risk to individuals.

Data Protection Impact Assessment

A structured assessment required before high-risk processing, such as large-scale health data processing, documenting necessity, proportionality, risks, and mitigating measures.

Controller versus processor

A controller determines the purposes and means of processing; a processor acts only on documented controller instructions. Exceeding those instructions makes the processor a controller.

Role-based access control

Access model assigning permissions to roles rather than individuals. Users receive roles matching job function, simplifying provisioning, review, and revocation at scale.

Break-glass access

Emergency access override allowing clinicians to reach records outside normal authorization. It must be time-limited, reason-coded, alerted in real time, and reviewed afterward.

Phishing-resistant MFA

Authentication bound to the legitimate service origin, such as FIDO2/WebAuthn security keys or passkeys, which resist credential interception and real-time relay attacks unlike SMS codes.

Least privilege

Principle granting users only the minimum access necessary for their duties, reducing the blast radius of compromised accounts and limiting unauthorized health record exposure.

Access recertification

Periodic managerial attestation that each user's entitlements remain appropriate. Orphaned, dormant, and excessive accounts identified during review are disabled or corrected.

Network segmentation

Dividing networks into zones with enforced traffic controls between them, isolating clinical devices, medical IoT, guest, and corporate systems to limit lateral movement after compromise.

Zero trust architecture

Security model requiring explicit verification of identity and device posture for every request, applying least privilege and assuming breach rather than trusting network location.

TLS version baseline

TLS 1.2 is the minimum acceptable version, with TLS 1.3 preferred. SSLv3 and TLS 1.0/1.1 are disabled because of known cryptographic weaknesses.

DMARC

Email authentication policy built on SPF and DKIM that tells receiving servers how to handle messages failing alignment checks, reducing domain spoofing and phishing.

Endpoint detection and response

Security tooling that continuously monitors endpoint behavior, detects malicious activity through analytics, and enables isolation, investigation, and remediation of compromised hosts.

Software bill of materials

Machine-readable inventory of software components and dependencies, commonly in SPDX or CycloneDX format, enabling rapid identification of exposure when a vulnerability is disclosed.

SQL injection defense

Parameterized queries separate SQL code from data, preventing attacker input from altering query structure. Input validation and least-privilege database accounts add defense in depth.

Secure SDLC

Integrating security activities into each development phase: threat modeling at design, SAST during coding, DAST in testing, and dependency scanning throughout the lifecycle.

Password hashing

Storing passwords using salted, deliberately slow algorithms such as bcrypt, scrypt, or Argon2. Fast hashes like plain SHA-256 are unsuitable because they enable rapid offline cracking.

SMART on FHIR

Authorization framework combining OAuth 2.0 with HL7 FHIR, using scopes to grant apps granular, patient-context access to clinical resources over encrypted transport.

Key rotation

Periodic replacement of cryptographic keys to limit the exposure window if a key is compromised, requiring documented generation, distribution, archival, and destruction procedures.

Digital signature

Cryptographic value created with a private key that verifies message integrity and signer authenticity, providing non-repudiation when backed by a trusted certificate chain.

Incident response phases

NIST SP 800-61 sequence: preparation; detection and analysis; containment, eradication, and recovery; and post-incident activity including lessons learned and corrective actions.

Chain of custody

Documented record tracking who handled evidence, when, and how, ensuring forensic integrity and admissibility. Volatile data such as memory is captured before disk imaging.

Recovery time objective

The maximum acceptable duration of service disruption for a process, established through business impact analysis and used to select recovery strategies and site types.

Recovery point objective

The maximum acceptable amount of data loss measured in time, determining backup frequency and replication design for critical clinical systems.

Immutable backup

Backup copies that cannot be altered or deleted during a defined retention period, protecting recovery capability against ransomware that targets connected backup systems.

Shared responsibility model

Cloud division of duties: the provider secures underlying infrastructure, while the customer secures identity, configuration, data classification, and access controls.