# sensitive data Sensitive data is personal data belonging to special categories that receive enhanced protection, including information about health, sexual life or orientation, racial or ethnic origin, political or religious beliefs, biometric or genetic data, and trade union membership. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CrowdStrike Accelerates Real-Time Data Classification with On-Device AI DevFeed: [CrowdStrike Accelerates Real-Time Data Classification with On-Device AI]() Original publisher: [Read original article]() Author: Lior Ribak Published: 2026-09-17T01:38:53.400452Z Content type: article Language: en Sources: [Blog]() Topics: [On-device AI](), [sensitive data](), [Language models](), [Endpoint security](), [Hardware](), [intel]() Tags: [data-security](), [endpoint-security](), [intel](), [language-models](), [npu](), [on-device-ai]() ### AI overview CrowdStrike and Intel introduced a Falcon Data Security capability that uses language models running on-device on dedicated AI hardware to classify sensitive data. The article explains that local inference is intended to avoid cloud latency and keep sensitive customer data on the endpoint while meeting real-time protection requirements. ### Source excerpt CrowdStrike worked closely with Intel to introduce a new capability in Falcon Data Security that classifies sensitive data using language models that run on-device using dedicated hardware for AI. Learn more! ## Native Splunk brings real-time insights to Cisco Nexus One DevFeed: [Native Splunk brings real-time insights to Cisco Nexus One]() Original publisher: [Read original article]() Author: David Keith Published: 2026-09-16T15:00:59Z Content type: release Language: en Sources: [Cisco Blogs]() Topics: [Nexus Dashboard](), [observability](), [telemetry](), [datacenter](), [Security](), [sensitive data](), [audit](), [configuration]() Tags: [analytics](), [audit](), [cisco](), [cisco-nexus-dashboard](), [configuration](), [data-center](), [data-center-networking](), [network](), [nexus-one](), [observability](), [real-time](), [sensitive-data](), [splunk](), [troubleshooting]() ### AI overview Cisco describes native Splunk embedded in Cisco Nexus Dashboard as an on-premises analytics and observability capability for data center and AI workloads. It processes telemetry locally, correlates network, security, configuration, and audit data, and provides dashboards, searches, and alerts for troubleshooting, data sovereignty, compliance, and cost efficiency. ### Source excerpt Discover how native Splunk embedded in Cisco Nexus Dashboard delivers real-time analytics, faster troubleshooting, and on-premises data sovereignty for modern data center and AI workloads. ## Atomic macOS (AMOS) Stealer Activity DevFeed: [Atomic macOS (AMOS) Stealer Activity]() Original publisher: [Read original article]() Author: Bradley Duncan Published: 2026-09-16T10:00:06Z Content type: article Language: en Sources: [Unit 42]() Topics: [Malware](), [Aeternum](), [macOS](), [sensitive data](), [Zsh](), [ClickFix](), [cURL]() Tags: [ads](), [clickfix](), [credentials](), [cryptocurrency](), [curl](), [general](), [insights](), [macos](), [malware](), [sensitive-data](), [threat-intelligence](), [unit-42](), [zsh]() ### AI overview This article analyzes a laboratory-generated Atomic macOS (AMOS) stealer infection observed on Aug. 5, 2026. It describes a deceptive macOS toolkit installation page that led users to paste a command into Terminal, retrieving a Zsh script containing an encoded compressed payload and a follow-up script designed to run a Mach-O binary. AMOS targets macOS and can exfiltrate system information, login credentials, and sensitive data from applications including browsers and cryptocurrency wallets. ### Source excerpt Modern macOS malware uses deceptive setup guides to steal credentials and sensitive user data. Learn how to identify and block these threats. The post Atomic macOS (AMOS) Stealer Activity appeared first on Unit 42. ## Progressive Authentication for Production-Ready RAG Architectures DevFeed: [Progressive Authentication for Production-Ready RAG Architectures]() Original publisher: [Read original article]() Author: Aishwarya Murali Padikkal Published: 2026-09-08T07:16:00Z Content type: article Language: en Sources: [Data Science at Microsoft]() Topics: [Authentication](), [Retrieval Augmented Generation (RAG)](), [sensitive data](), [User Experience](), [Security]() Tags: [ai](), [ai-agent](), [authentication](), [data-science](), [privacy](), [rag](), [retrieval](), [sensitive-data](), [user-experience]() ### AI overview The article presents progressive authentication for RAG systems: answer public questions without sign-in, then authenticate within the conversation when a request requires access to sensitive personal data. It argues that static, upfront authentication does not fit conversations that shift between public and private contexts. ### Source excerpt Designing a production-ready RAG architecture where authentication becomes part of the conversation, not a prerequisite for it. By Aishwarya Murali Padikkal & Priyank Solanki From understanding to retrieval, grounding, and response, authentication enters only when the conversation requires access to sensitive data- illustrating the core idea of progressive authentication. Illustration generated using ChatGPT and refined by the authors. Two questions, one help line Imagine two taxpayers opening the same AI-powered tax assistant. The first asks, "When is the filing deadline this year?" The second asks, "What was my refund last year?" Both questions are valid. Both deserve fast, helpful answers. Yet they represent fundamentally different types of requests. Figure 1. The same assistant, two different journeys. Requests are routed according to the type of information being accessed. Illustration generated by AI (ChatGPT) and refined by the authors. The answer to the first lives in a public handbook. Anyone should be able to access it instantly- no sign-in, no friction. The answer to the second is within an individual's private tax records. Before revealing a single detail, the assistant must be certain it is interacting with the right person. Making public information instantly accessible while ensuring private information is revealed only to the right person, all within the same conversation, is the challenge we set out to solve. It is also where conventional RAG systems quietly fall apart. Traditional RAG architectures assume a much simpler interaction model: a user asks a question, the system retrieves relevant documents, and the model generates an answer. Authentication, if it exists at all, is treated as a one-time checkpoint at the start of the interaction. Real conversations are far less predictable. Users naturally shift contexts, starting with a public question, moving to a personal one, and then asking follow-up questions that rely on both. The conversation evo ## From one switch to a control panel: meet \`dataCollection\` DevFeed: [From one switch to a control panel: meet \`dataCollection\`]() Original publisher: [Read original article]() Author: Sigrid Huemer Published: 2026-08-28T09:00:00Z Content type: release Language: en Sources: [Sentry Blog]() Topics: [SDKs](), [data](), [JavaScript](), [sensitive data](), [Release notes](), [passwords]() Tags: [api-keys](), [data](), [javascript](), [passwords](), [release-notes](), [sdks](), [sensitive-data]() ### AI overview Sentry is replacing the all-or-nothing `sendDefaultPii` setting with `dataCollection`, which provides granular control over automatically collected data such as user information, headers, request bodies, and GenAI data. The change is rolling out across Sentry SDKs, with JavaScript SDK v11 making it the default and collecting more data than v10 by default. ### Source excerpt Sentry SDKs replace the `sendDefaultPii` boolean with `dataCollection`, granular options for user data, headers, bodies, GenAI data, and more. ## How to evaluate session replay software: a developer's guide DevFeed: [How to evaluate session replay software: a developer's guide]() Original publisher: [Read original article]() Author: Lindsay Piper Published: 2026-08-26T09:00:00Z Content type: tutorial Language: en Sources: [Sentry Blog]() Topics: [session replay](), [Playback](), [sensitive data](), [debugging](), [Mobile]() Tags: [debug](), [debugging](), [developer](), [engineering](), [guide](), [libraries](), [monitoring](), [mutation](), [playback](), [privacy](), [sdk](), [sensitive-data](), [session-replay](), [tool](), [ux]() ### AI overview A developer guide to evaluating session replay software by comparing recording methods, privacy architecture, error-monitoring integration, overhead, AI debugging compatibility, and mobile support. It distinguishes UX analytics tools from developer debugging tools and explains the tradeoffs between DOM snapshot recording and pixel capture. ### Source excerpt Compare session replay tools on recording methodology, privacy architecture, integration depth, overhead, AI-readability, and mobile support ## Migrating to Auth0 for Startups from Another Auth Solution DevFeed: [Migrating to Auth0 for Startups from Another Auth Solution]() Original publisher: [Read original article]() Author: Shreya Gupta Published: 2026-08-26T00:00:00Z Content type: article Language: en Sources: [Auth0 Blog]() Topics: [Auth0](), [Security](), [sensitive data]() Tags: [auth0](), [security](), [sensitive-data](), [startups]() ### AI overview An interview with Evenpay's CTO describes the startup's migration from another authentication provider to Auth0 after Finnish customers required EU data residency controls and compliance configuration. The article discusses securing sensitive salary data and says the customer migration took a few weeks with support materials and AI assistance. ### Source excerpt Interviewing Evenpay on building trust from day one. ## How to Use GitHub Actions to Deploy to Kubernetes Without Shared Secrets DevFeed: [How to Use GitHub Actions to Deploy to Kubernetes Without Shared Secrets]() Original publisher: [Read original article]() Author: info@goteleport.com (Noah Stride) Published: 2026-08-05T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [GitHub Actions](), [Kubernetes](), [Security](), [sensitive data](), [Vulnerabilities]() Tags: [ci-cd](), [github](), [github-actions](), [how-to](), [kubernetes](), [secrets](), [security](), [sensitive-data]() ### AI overview This tutorial explains how to use Teleport and GitHub Actions to deploy applications to Kubernetes without shared, long-lived credentials. It covers short-lived identities, Kubernetes RBAC, Teleport roles, and join tokens, and discusses extending the approach to database connections and internal APIs. ### Source excerpt Learn how use GitHub Actions to deploy to Kubernetes using short-lived, verifiable identities. ## Lambda-powered functions land in OTTL DevFeed: [Lambda-powered functions land in OTTL]() Original publisher: [Read original article]() Author: OpenTelemetry Authors; Docs CC BY Published: 2026-07-22T20:04:49Z Content type: release Language: en Sources: [Blog on OpenTelemetry]() Topics: [OpenTelemetry](), [telemetry](), [sensitive data](), [data]() Tags: [collection-operations](), [experimental](), [functions](), [lambda](), [opentelemetry](), [pipelines](), [release](), [sensitive-data](), [telemetry](), [transformation]() ### AI overview OpenTelemetry Collector Contrib v0.157.0 introduces lambda expressions to OTTL, enabling reusable inline logic in generic higher-order functions. The release adds eight experimental functions for collection transformations, including filtering, mapping, finding, reducing, and conditional operations. ### Source excerpt As telemetry pipelines become more sophisticated, so do the transformations they need to perform: sanitizing sensitive data, normalizing inconsistent schemas, and enforcing attribute contracts. While OTTL provides a rich set of transformation functions, expressing collection operations has required dedicated functions with hardcoded behavior for each new use case. OpenTelemetry Collector Contrib v0.157.0 changes that by introducing lambda expressions to OTTL. Lambdas let users pass inline logic directly to generic higher-order functions, making complex collection transformations both reusable and concise. The release includes eight new functions that leverage this capability: Filter, MapEach, MapKeys, Any, All, Find, Reduce, and When. ## Kan een Amerikaans bedrijf met encryptie de Amerikaanse overheid buiten de deur houden? DevFeed: [Kan een Amerikaans bedrijf met encryptie de Amerikaanse overheid buiten de deur houden?]() Original publisher: [Read original article]() Published: 2026-07-21T13:20:00Z Content type: opinion Language: nl Sources: [Bert Hubert's writings]() Topics: [Encryption](), [sensitive data](), [Microsoft](), [servers](), [Malware]() Tags: [encryption](), [microsoft](), [requirements](), [sensitive-data](), [server]() ### AI overview This Dutch commentary examines whether encryption can prevent the United States from accessing data held or processed by partly American companies. It argues that services such as Microsoft Double Key Encryption are difficult to use for ordinary data because servers need access to plaintext for searching and other operations, and that administrators ultimately retain significant control over server data. ### Source excerpt Het is inmiddels duidelijk dat zelfs maar deels Amerikaanse bedrijven met allerhande middelen gedwongen kunnen worden om onze data te overhandigen aan de Amerikaanse overheid. Ook kan de dienstverlening gestaakt worden na een enkel briefje op Whitehouse.gov, wat zonder enige rechterlijke toetsing geplaatst kan worden. Tegen deze beide dingen is met papier niets te doen. Geen speciale afspraak zal je redden uit dit probleem (dit ook volgens de Landsadvocaat). Maar, er is dan soms nog de hoop om de data nog wel privé te houden met speciale encryptie. ## Securing Heroku CLI Credentials with System Keychain Storage DevFeed: [Securing Heroku CLI Credentials with System Keychain Storage]() Original publisher: [Read original article]() Author: Katy Bowman Published: 2026-07-01T21:11:54Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Authentication](), [Command-line interface](), [Security](), [sensitive data]() Tags: [authentication](), [cli](), [compatibility](), [credentials](), [engineering](), [heroku](), [linux](), [macos](), [security](), [sensitive-data](), [storage](), [windows]() ### AI overview Heroku CLI version 11.8.0 makes system keychain storage the default for authentication credentials. The credential manager uses native secure storage on macOS, Linux, and Windows while preserving netrc compatibility and file-based fallback options. ### Source excerpt Beginning in version 11.8.0, we will be improving the security of the Heroku CLI by storing authentication credentials in your system keychain by default. The Heroku credential manager makes use of OS-native secure storage tools with interfaces designed for sensitive data while maintaining compatibility with existing developer workflows. We began the transition to our new [...] The post Securing Heroku CLI Credentials with System Keychain Storage appeared first on Heroku. ## How XY builds an AI agent orchestration platform for healthcare with Temporal DevFeed: [How XY builds an AI agent orchestration platform for healthcare with Temporal]() Original publisher: [Read original article]() Author: The XY Engineering Team Published: 2026-04-23T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [agent orchestration](), [AI Agent](), [Orchestration](), [reliability](), [human review](), [sensitive data](), [Structured-data](), [YAML]() Tags: [agent](), [agent-orchestration](), [ai](), [ai-agent](), [automation](), [how-to](), [human-review](), [long-running](), [orchestration](), [reliability](), [sensitive-data](), [temporal](), [workflow]() ### AI overview XY describes using Temporal as a DSL-driven execution engine for an AI agent orchestration platform serving complex healthcare workflows. The approach uses a YAML-based workflow language and a generic Temporal workflow class to coordinate multiple systems, reliability features, human review, and sensitive healthcare data from prototype to production. ### Source excerpt One generic Temporal workflow class can provide infinite healthcare automation. See how XY built a DSL-driven AI agent orchestration platform that scales from prototype to production. ## Managing Sensitive Data in jOOQ 3.21+ Logs DevFeed: [Managing Sensitive Data in jOOQ 3.21+ Logs]() Original publisher: [Read original article]() Author: lukaseder Published: 2026-03-27T12:45:19Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Logging](), [sensitive data](), [Security](), [configuration](), [Code]() Tags: [configuration](), [csv](), [debug-logging](), [jooq](), [jooq-in-use](), [json](), [logging](), [logs](), [maven](), [redacted-columns](), [security](), [sensitive-data](), [xml]() ### AI overview This article explains how jOOQ debug logging can expose query bind values and fetched records in application logs, creating security concerns in production. It describes a code-generation configuration available in commercial jOOQ distributions to mask exported data, including text, HTML, and optionally CSV, JSON, or XML output. ### Source excerpt One of jOOQ's most popular feature is the out-of-the-box debug logging experience. jOOQ developers find this feature very useful when developing their applications. Assuming you run a jOOQ query and configure your logger to print DEBUG log output: When this query is executed, your log output might contain something like this: Executing query : select ... Continue reading Managing Sensitive Data in jOOQ 3.21+ Logs -> ## Sandbox Your AI Dev Tools: A Practical Guide for VMs and Lima DevFeed: [Sandbox Your AI Dev Tools: A Practical Guide for VMs and Lima]() Original publisher: [Read original article]() Author: Chris Hager Published: 2025-11-25T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [AI-assisted coding](), [developer tooling](), [virtual machines](), [sensitive data](), [API keys](), [ssh](), [npm](), [pip]() Tags: [ai-assisted-coding](), [api-keys](), [dev-tools](), [npm](), [python](), [sandbox](), [sensitive-data](), [ssh]() ### AI overview A practical guide to sandboxing AI coding assistants and other development tools in isolated virtual machines using Lima. It explains how isolation helps protect SSH keys, API tokens, credentials, environment variables, and other sensitive data from arbitrary code, scripts, and package installation behavior. ### Source excerpt AI coding assistants, npm, pip, and other development tools can run arbitrary code and scripts on your machine, potentially stealing SSH keys, API tokens, wallet keys, sensitive credentials and other private data without you noticing. This guide shows you how to sandbox these tools in isolated VMs using Lima, so you can experiment and develop freely without putting your sensitive data at risk. Jump straight to the guide, or read on for a bit of personal context. ## How to protect sensitive data in a Temporal Application DevFeed: [How to protect sensitive data in a Temporal Application]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2025-10-09T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [sensitive data](), [Security](), [payload](), [TLS (Transport Layer Security)](), [observability](), [ui](), [Command-line interface]() Tags: [cli](), [how-to](), [observability](), [payload](), [security](), [sensitive-data](), [temporal-concepts](), [tls](), [ui]() ### AI overview This tutorial explains how to protect sensitive data in Temporal applications. It describes Temporal's layered data-security approach, including TLS, Payload Codecs, and a Codec Server, while preserving observability through the Web UI and CLI. ### Source excerpt Learn how to protect sensitive data in Temporal apps using TLS, Payload Codecs, and a Codec Server without losing Web UI or CLI observability. ## Data Safety Levels Framework: The foundation of how we look at data in Block DevFeed: [Data Safety Levels Framework: The foundation of how we look at data in Block]() Original publisher: [Read original article]() Author: John Rogers Published: 2025-01-16T00:00:00Z Content type: article Language: en Sources: [Cash App Code Blog]() Topics: [data](), [sensitive data](), [pii](), [context](), [Requirements](), [systems]() Tags: [context](), [customer-trust](), [data](), [engineering](), [pii](), [requirements](), [security-governance](), [sensitive-data](), [standards]() ### AI overview Block introduces its Data Safety Levels (DSL) Framework, a system for evaluating data sensitivity in context and building scalable, automated data-management policies across Cash App, Square, and TIDAL. ### Source excerpt Block uses the Data Safety Levels (DSL) Framework to evaluate data sensitivity. ## Detect Hardcoded Secrets Early to Reduce Data Breach Risk DevFeed: [Detect Hardcoded Secrets Early to Reduce Data Breach Risk]() Original publisher: [Read original article]() Author: Liran Tal Published: 2024-09-16T05:00:00Z Content type: tutorial Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Development](), [sensitive data](), [Security](), [API keys](), [snyk](), [Authentication](), [passwords](), [JSON Web Tokens](), [ide](), [JavaScript]() Tags: [access-control](), [api-keys](), [application-security](), [authentication](), [awareness](), [blog](), [breach](), [code-security](), [developer](), [devops](), [devrel](), [devsecops](), [iac-security](), [javascript](), [jwt](), [passwords](), [secrets](), [security](), [sensitive-data](), [snyk-code](), [snyk-security-intel](), [supply-chain-security](), [vulnerability-insights]() ### AI overview This developer article explains that hardcoded secrets, including API keys, database credentials, passwords, encryption keys, and tokens, can expose applications to unauthorized access and data breaches. It describes using secrets detection during development to identify exposed credentials early, including through the Snyk IntelliJ IDE extension. ### Source excerpt Concerned about data breaches? Exposed secrets like API keys and passwords are a major culprit. Secure your software development lifecycle, identify and remove hardcoded secrets in code, and leverage Snyk's secrets detection tools to identify secrets early in development in order to prevent breaches and safeguard your applications. ## Mintlify's security improvements after the March 2024 incident DevFeed: [Mintlify's security improvements after the March 2024 incident]() Original publisher: [Read original article]() Author: Han Wang Published: 2024-03-22T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [Security](), [Vulnerabilities](), [Encryption](), [incident](), [OAuth](), [Authentication](), [sensitive data]() Tags: [announcements](), [authentication](), [data](), [encryption](), [incident](), [oauth](), [privacy](), [security](), [security-vulnerabilities]() ### AI overview Mintlify describes security improvements made in response to a March 2024 security incident, including AES256-GCM encryption at rest, changes to GitHub OAuth token handling, removal of internal admin tokens, and session-based access controls. ### Source excerpt We at Mintlify are committed to the privacy and security of our customers. Your trust in our ability to safeguard your data is the cornerstone upon which our services are built. ## Seamlessly integrate with partners to enhance the travel experience DevFeed: [Seamlessly integrate with partners to enhance the travel experience]() Original publisher: [Read original article]() Author: Tushar Bhushan Published: 2023-07-14T12:48:06Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [GraphQL](), [API](), [sensitive data](), [configuration](), [Deployment]() Tags: [api](), [configuration](), [deployment](), [graphos](), [graphql](), [how-to](), [integrations](), [sensitive-data]() ### AI overview This tutorial explains how travel companies can use Apollo GraphOS to integrate third-party services. It discusses GraphQL and REST integration challenges, schema contracts, demand control, field-level metrics, and selectively excluding sensitive data from third-party APIs. ### Source excerpt This post is a part of our "How to build connected travel apps with Apollo GraphOS" series. Also in this series: - Delivering personalized travel experiences with GraphQL - Ship products faster with SDUI - Mitigate scraping and bot attacks with GraphOS Travel companies often strive to enhance their services by collaborating with third-party providers through API integrations. ## SiriSpy - iOS bug allowed apps to eavesdrop on your conversations with Siri DevFeed: [SiriSpy - iOS bug allowed apps to eavesdrop on your conversations with Siri]() Original publisher: [Read original article]() Published: 2022-10-26T16:00:00Z Content type: article Language: en Sources: [Rambo Codes]() Topics: [iOS](), [bug](), [Security](), [sensitive data](), [Reverse Engineering]() Tags: [bluetooth](), [bug](), [ios](), [reverse-engineering](), [security](), [security-and-privacy](), [sensitive-data]() ### AI overview The article describes an iOS bug that allowed apps with Bluetooth access to record conversations with Siri and audio from keyboard dictation when users wore AirPods or Beats headsets. Recording could occur without microphone permission and without leaving a listening trace. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. ## An Introduction to Hardware Security Modules (HSMs) DevFeed: [An Introduction to Hardware Security Modules (HSMs)]() Original publisher: [Read original article]() Author: info@goteleport.com (Russell Jones) Published: 2021-08-31T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Security](), [private key](), [sensitive data](), [remote access](), [certificates]() Tags: [certificates](), [private-key](), [remote-access](), [security](), [sensitive-data]() ### AI overview This article explains how hardware security modules protect sensitive data such as private keys by exposing cryptographic operations instead of allowing the data to be read. It describes Teleport 7.2 support for HSMs and how they can reduce the risk of private-key theft in remote-access clusters, while noting that HSMs do not mitigate every attack vector. ### Source excerpt In this blog post we explain how hardware security modules (HSM) help protect sensitive data and how Teleport 7.2 uses HSM to make remote access more secure. ## Apache Airflow 1.10.12 DevFeed: [Apache Airflow 1.10.12]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2020-08-25T00:00:00Z Content type: release Language: en Sources: [Apache Airflow Blog]() Topics: [airflow](), [sensitive data](), [Amazon S3](), [HashiCorp Vault](), [Kubernetes]() Tags: [airflow](), [apache](), [apache-airflow](), [bug-fixes](), [changelog](), [class](), [improvements](), [kubernetes](), [new-features](), [pypi](), [release](), [s3](), [secrets](), [sensitive-data](), [upgrade](), [vault]() ### AI overview Apache Airflow 1.10.12 is a release containing 113 commits since 1.10.11, including new features, improvements, bug fixes, and documentation changes. It adds custom XCom classes, secret-backed configuration for sensitive values, and AirflowClusterPolicyViolation support in local settings. The article recommends upgrading directly to 1.10.12 because Airflow 1.10.11 introduced breaking changes related to KubernetesExecutor and KubernetesPodOperator. ### Source excerpt Airflow 1.10.12 contains 113 commits since 1.10.11 and includes 5 new features, 23 improvements, 23 bug fixes, and several doc changes. Details: PyPI: https://pypi.org/project/apache-airflow/1.10.12/ Docs: https://airflow.apache.org/docs/1.10.12/ Changelog: http://airflow.apache.org/docs/1.10.12/changelog.html Airflow 1.10.11 has breaking changes with respect to KubernetesExecutor & KubernetesPodOperator so I recommend users to directly upgrade to Airflow 1.10.12 instead. Some of the noteworthy new features (user-facing) are: Allow defining custom XCom class Get Airflow configs with sensitive data from Secret Backends Add AirflowClusterPolicyViolation support to Airflow local settings Allow defining Custom XCom class Until Airflow 1.10.11, the XCom data was only stored in Airflow Metadatabase. From Airflow 1.10.12, users would be able to define custom XCom classes. This will allow users to transfer larger data between tasks. An example here would be to store XCom in S3 or GCS Bucket if the size of data that needs to be stored is larger than XCom.MAX_XCOM_SIZE (48 KB). PR: https://github.com/apache/airflow/pull/8560 Get Airflow configs with sensitive data from Secret Backends Users would be able to get the following Airflow configs from Secrets Backend like Hashicorp Vault: sql_alchemy_conn in [core] section fernet_key in [core] section broker_url in [celery] section flower_basic_auth in [celery] section result_backend in [celery] section password in [atlas] section smtp_password in [smtp] section bind_password in [ldap] section git_password in [kubernetes] section Further improving Airflow's Secret Management story, from Airflow 1.10.12, users don't need to hardcode the sensitive config value in airflow.cfg nor then need to use an Environment variable to set this config. For example, the metadata database connection string can either be set in airflow.cfg like this: [core] sql_alchemy_conn_secret = sql_alchemy_conn This will retrieve config option from the set Secre ## Threat Modeling with Questionnaires DevFeed: [Threat Modeling with Questionnaires]() Original publisher: [Read original article]() Author: Adam Published: 2020-03-19T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Application Security](), [Security](), [self-service](), [sensitive data]() Tags: [appsec](), [security](), [self-service](), [sensitive-data]() ### AI overview The article examines lightweight threat modeling through self-service security questionnaires. It argues that developers or scrum masters can identify what they are building, what could go wrong, and whether security engineers should focus on the feature based on its risk. ### Source excerpt This post comes from a conversation I had on Linkedin with Clint Gibler. ## Common pitfalls when using Keychain Sharing on iOS DevFeed: [Common pitfalls when using Keychain Sharing on iOS]() Original publisher: [Read original article]() Published: 2020-01-16T14:00:00Z Content type: tutorial Language: en Sources: [Rambo Codes]() Topics: [iOS](), [Xcode](), [Authentication](), [coding](), [sensitive data]() Tags: [authentication](), [coding](), [ios](), [pitfalls](), [sensitive-data](), [xcode]() ### AI overview An article about common Keychain Sharing problems on iOS, including incorrect group names and limitations of using Keychain Sharing in the iOS Simulator. It also discusses checking entitlements in the final binary with jtool. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. [Next page]()