SShortSingh.
Back to feed

Field-level encryption: choosing the layer that has to hold

0
·1 views

Field-level encryption: choosing the layer that has to hold Encryption at rest protects the storage medium. It does not protect the running application, and it does not limit which records a compromised service account can read. Field-level encryption moves the protection boundary upward: selected values are encrypted before they reach the database, so a dump of the table shows ciphertext for those columns only. The standard pattern uses a data encryption key (DEK) to encrypt each record and a key encryption key (KEK) held in a key management service to wrap that DEK. NIST SP 800-57 Part 1 Rev

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Merge many Excel/CSV files into one sheet: Power Query steps and 3 gotchas

Every month someone sends you twelve branch reports, or a folder of CSV exports, and you spend an hour copy-pasting them into one sheet. Excel already has a built-in way to do this: Power Query. Here is the short version, plus three things that usually break it. Put all files you want to merge in one folder (nothing else in it). In a new workbook: Data > Get Data > From File > From Folder, pick the folder.

0
ProgrammingDEV Community ·

Cloudflare Adds Web Search to AI Gateway for Grounding Agent Responses

Cloudflare has added a native Web Search API to its AI Gateway, built in partnership with search providers Ceramic.ai, Exa, and Linkup. The feature lets developers pull live web results into a model's context window during inference, addressing the gap where models are frozen at a training cutoff and can't speak to recent events or changing documentation. Three access paths are available: directly through AI Gateway, via a standard REST endpoint (passing an AI Gateway auth token and a provider name in the request payload), or through a Workers binding that Cloudflare says takes one line of cod

0
ProgrammingDEV Community ·

Cross-Chain Bridge Risk Assessment: CCIP

Cross-Chain Bridge Risk Assessment: CCIP Target Protocol: CCIP (TVL: $1862.7M) Chainlink Cross‑Chain Interoperability Protocol (CCIP) TVL (Ethereum & L2s): ≈ $1.86 B (Oct 2026) CCIP is Chainlink’s flagship cross‑chain messaging and token‑transfer layer, designed to enable developers to move arbitrary data and assets between EVM‑compatible chains, L2 roll‑ups, and non‑EVM networks. Its architecture relies on a decentralised network of off‑chain relayers (oracles), on‑chain router contracts, messenger contracts on each destination chain, and liquidity pools (or “Liquidity Providers – LPs”) that

Field-level encryption: choosing the layer that has to hold · ShortSingh