---
title: "Discussion on \"Apex CRUD and FLS: SECURITY_ENFORCED vs stripInaccessible\" | Hashnode"
description: "Discussion on \"Apex CRUD and FLS: SECURITY_ENFORCED vs stripInaccessible\". Apex code that reads or writes records can bypass field-level security and CRUD permissions by default. Two patterns enforce these checks, each with different ergonomics and audit implications. Picking the right one matters for AppExchange"
url: "https://hashnode.com/posts/apex-crud-and-fls-securityenforced-vs-stripinaccessible/6a53c4af7370acb718591fae"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Apex CRUD and FLS: SECURITY\_ENFORCED vs stripInaccessible](https://sapotacorpvn.hashnode.dev/apex-crud-and-fls-securityenforced-vs-stripinaccessible?utm_source=hashnode&utm_medium=feed)

Apex code that reads or writes records can bypass field-level security and CRUD permissions by default. Two patterns enforce these checks, each with different ergonomics and audit implications. Picking the right one matters for AppExchange

Jul 12 · 7 min read · sapotacorpvn.hashnode.dev  
Read the article

-   [#salesforce](https://hashnode.com/tag/salesforce)
-   [#apex](https://hashnode.com/tag/apex)
-   [#security](https://hashnode.com/tag/security)
-   [#crud-fls](https://hashnode.com/tag/crud-fls)
-   [#apex-development](https://hashnode.com/tag/apex-development)

## Written by

[SapotaCorp](https://hashnode.com/@sapotacorpvn)

@sapotacorpvn · Hanoi, Vietnam

  
[View profile](https://hashnode.com/@sapotacorpvn)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.