Angular Munich – Telegram
Angular Munich
180 subscribers
554 photos
41 videos
9 files
705 links
Stay up to date with Angular Framework ;-)

Need more: https://linktr.ee/ngxsamurai
Download Telegram
🔥🔥🔥 angular v17

- new logo
- new web site for documentation(https://angular.dev/)
- finished tasks with hydration (SSR)
- new syntax „Control Flow“
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥21
Angular 17 live!! 🔥
Angular Munich pinned «Angular 17 live!! 🔥»
Angular Munich pinned «https://massivepixel.io/blog/angular-best-practices/»
🚀 The Ultimate Angular Adapter for TanStack Query | by Netanel Basal | Nov, 2023 | Netanel Basal
https://netbasal.com/the-ultimate-angular-adapter-for-tanstack-query-fac41b244c6f
Angular Official Docs are pretty great! Security in #Angular is important! 🔐

Things you should remember!!! 👇

🔐 Best Practices

➼ Stay updated with Angular library releases.
➼ Avoid altering Angular core
➼ Steer clear of APIs marked "Security Risk".

🔐 XSS Prevention

➼ Block malicious code entry to DOM.
➼ Angular treats all values as untrusted by default.
➼ Sanitizes values inserted into DOM from templates.
➼ Templates are trusted; avoid creating them with user input.

🔐 Sanitization and Security Contexts

➼ Angular sanitizes values for HTML, styles, URLs.
➼ Context-specific: HTML, Style, URL, Resource URL.
➼ Development mode warnings for sanitization changes.

🔐 Direct DOM API Use & Explicit Sanitization

➼ Use Angular templates over direct DOM interaction.
➼ For unavoidable cases, use Angular sanitization functions.

🔐 Trusting Safe Values

➼ Use DomSanitizer for necessary executable code or URLs.
➼ Context-specific methods liek bypassSecurityTrustHtml.

🔐 Content Security Policy (CSP)

➼ Prevents XSS via web server configuration.
➼ Requires unique per-request nonces for Angular to render styles.

🔐 Enforcing Trusted Types

Use HTTP headers with one of the following Angular Policies:
➼ angular
➼ angular#unsafe-bypass
➼ angular#unsafe-jit
➼ angular#bundler

🔐 Server-side XSS Protection

➼ Avoid creating Angular templates on the server side.
➼ Use templating languages that auto-escape values.

🔐 HTTP-level Vulnerabilities

➼ Built-in support for CSRF/XSRF and XSSI.
➼ Cooperate server and client for anti-XSRF technique.

🔐 Auditing Angular Applications

➼ Follow regular web app security principles.
➼ Audit Angular-specific APIs marked as sensitive.

More in depth look can be found in Docs: https://angular.dev/guide/security
Just ignore 😅
Please open Telegram to view this post
VIEW IN TELEGRAM