{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/check-the-selected-axis-pencil-filter-separately-from-its-settings/", "item": { "id": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/", "slug": "check-the-selected-axis-pencil-filter-separately-from-its-settings", "url": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings.md", "json": "https://update.dsesecurity.com/api/v1/posts/check-the-selected-axis-pencil-filter-separately-from-its-settings/" }, "title": "Check the selected Axis pencil filter separately from its settings", "summary": "Distinguish Axis pencil-filter settings from the selected active filter. Review the rendered result under an approved privacy requirement without claiming that a visual effect makes people anonymous.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "physical-security", "label": "Physical security", "alt": "Integrated video surveillance and controlled entry at a modern commercial facility.", "card_url": "https://update.dsesecurity.com/assets/editorial/physical-security-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/physical-security-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "video-surveillance", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-29T20:33:23+00:00", "modified_at": "2026-10-29T20:33:34+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 493, "potentially_affected": "Axis products exposing the documented Pencil privacy filter interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends reviewing filter parameters and active selection separately, then assessing each required image path with authorized observers.", "primary_source": { "name": "Axis Communications — Pencil privacy filter", "url": "https://developer.axis.com/vapix/network-video/pencil-privacy-filter/", "published_on": null, "authority": "Axis Communications" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Bottom line: Record both the settings and the selected filter before assessing the image. Verify the actual output against the owner’s requirement, and keep a successful configuration response separate from privacy acceptance.

\n

Source fact: documented behavior

\n

Axis’s Pencil privacy filter describes a monochrome pencil-image effect and exposes separate operations for filter settings, capabilities and selection.

\n

setFilterSettings changes the parameters of a filter type, while setSelectedFilter chooses which filter is active.

\n

The selection description says none deactivates the filter, and getSelectedFilter reports the current selection.

\n

What the source does not establish

\n

Do not infer anonymity, legal compliance or coverage of every image consumer from the API’s name. Confirm the actual supported filter and flags. Keep scene visibility, recording, exported images and the owner’s privacy requirement as separately observed acceptance questions.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

The following steps are DSE recommendations based on the cited source.

\n

DSE recommends reviewing filter parameters and active selection separately, then assessing each required image path with authorized observers.

\n
    \n
  1. Obtain the device’s actual capabilities, current settings and selected filter through the supported operations. Record those as separate fields. Ask the privacy and operational owners to define what the resulting image should reveal for the intended task, without replacing that requirement with an unsupported assertion that the filter removes identity.
    2. \n
  2. Prepare an authorized scene using harmless objects or expressly permitted participants and controlled image access. Set only approved supported parameters, then explicitly inspect the selected-filter result. Do not treat stored settings for a filter type as the evidence that the intended effect is currently selected.
    3. \n
  3. Observe each approved output path and compare it with the written requirement. Where recordings or exports are part of the scope, inspect those through the normal authorized workflow rather than relying on the live preview. Stop the acceptance if an unreviewed image remains accessible or the operational task cannot be performed, and restore the approved configuration through its supported process.
    4. \n
\n

Verification and evidence

\n

Retain the capability information, settings, selection readback and restricted observation record for each tested path. Have a reviewer identify which evidence establishes configuration and which establishes the owner’s image requirement. Avoid including identifiable test images in broadly shared tickets or configuration examples.

\n

Use a proposed desk case containing updated filter settings alongside a selection of none. Ask the reviewer to explain why those records cannot establish an active effect. Keep any privacy or legal assessment with the appropriate owner. This article reports no image test, privacy certification, anonymization result or observed recording behavior.

\n

Official references

\n\n

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.

\n", "content_text": "Bottom line: Record both the settings and the selected filter before assessing the image. Verify the actual output against the owner’s requirement, and keep a successful configuration response separate from privacy acceptance.\nSource fact: documented behavior\nAxis’s Pencil privacy filter describes a monochrome pencil-image effect and exposes separate operations for filter settings, capabilities and selection.\nsetFilterSettings changes the parameters of a filter type, while setSelectedFilter chooses which filter is active.\nThe selection description says none deactivates the filter, and getSelectedFilter reports the current selection.\nWhat the source does not establish\nDo not infer anonymity, legal compliance or coverage of every image consumer from the API’s name. Confirm the actual supported filter and flags. Keep scene visibility, recording, exported images and the owner’s privacy requirement as separately observed acceptance questions.\nApplicability questions\n\nWhich device, filter type and supported flags are actually available?\nWhat current settings and active selection does it report?\nWhich live, recorded or exported paths are within the approved requirement?\nWho may inspect the test images and decide whether the result is acceptable?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends reviewing filter parameters and active selection separately, then assessing each required image path with authorized observers.\n\nObtain the device’s actual capabilities, current settings and selected filter through the supported operations. Record those as separate fields. Ask the privacy and operational owners to define what the resulting image should reveal for the intended task, without replacing that requirement with an unsupported assertion that the filter removes identity.\nPrepare an authorized scene using harmless objects or expressly permitted participants and controlled image access. Set only approved supported parameters, then explicitly inspect the selected-filter result. Do not treat stored settings for a filter type as the evidence that the intended effect is currently selected.\nObserve each approved output path and compare it with the written requirement. Where recordings or exports are part of the scope, inspect those through the normal authorized workflow rather than relying on the live preview. Stop the acceptance if an unreviewed image remains accessible or the operational task cannot be performed, and restore the approved configuration through its supported process.\n\nVerification and evidence\nRetain the capability information, settings, selection readback and restricted observation record for each tested path. Have a reviewer identify which evidence establishes configuration and which establishes the owner’s image requirement. Avoid including identifiable test images in broadly shared tickets or configuration examples.\nUse a proposed desk case containing updated filter settings alongside a selection of none. Ask the reviewer to explain why those records cannot establish an active effect. Keep any privacy or legal assessment with the appropriate owner. This article reports no image test, privacy certification, anonymization result or observed recording behavior.\nOfficial references\n\nPencil privacy filter — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "content_markdown": "Bottom line: Record both the settings and the selected filter before assessing the image. Verify the actual output against the owner’s requirement, and keep a successful configuration response separate from privacy acceptance.\n\n## Source fact: documented behavior\n\nAxis’s [Pencil privacy filter](https://developer.axis.com/vapix/network-video/pencil-privacy-filter/) describes a monochrome pencil-image effect and exposes separate operations for filter settings, capabilities and selection.\n\nsetFilterSettings changes the parameters of a filter type, while setSelectedFilter chooses which filter is active.\n\nThe selection description says none deactivates the filter, and getSelectedFilter reports the current selection.\n\n## What the source does not establish\n\nDo not infer anonymity, legal compliance or coverage of every image consumer from the API’s name. Confirm the actual supported filter and flags. Keep scene visibility, recording, exported images and the owner’s privacy requirement as separately observed acceptance questions.\n\n## Applicability questions\n\n- Which device, filter type and supported flags are actually available?\n\n- What current settings and active selection does it report?\n\n- Which live, recorded or exported paths are within the approved requirement?\n\n- Who may inspect the test images and decide whether the result is acceptable?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends reviewing filter parameters and active selection separately, then assessing each required image path with authorized observers.\n\n- Obtain the device’s actual capabilities, current settings and selected filter through the supported operations. Record those as separate fields. Ask the privacy and operational owners to define what the resulting image should reveal for the intended task, without replacing that requirement with an unsupported assertion that the filter removes identity.\n\n- Prepare an authorized scene using harmless objects or expressly permitted participants and controlled image access. Set only approved supported parameters, then explicitly inspect the selected-filter result. Do not treat stored settings for a filter type as the evidence that the intended effect is currently selected.\n\n- Observe each approved output path and compare it with the written requirement. Where recordings or exports are part of the scope, inspect those through the normal authorized workflow rather than relying on the live preview. Stop the acceptance if an unreviewed image remains accessible or the operational task cannot be performed, and restore the approved configuration through its supported process.\n\n## Verification and evidence\n\nRetain the capability information, settings, selection readback and restricted observation record for each tested path. Have a reviewer identify which evidence establishes configuration and which establishes the owner’s image requirement. Avoid including identifiable test images in broadly shared tickets or configuration examples.\n\nUse a proposed desk case containing updated filter settings alongside a selection of none. Ask the reviewer to explain why those records cannot establish an active effect. Keep any privacy or legal assessment with the appropriate owner. This article reports no image test, privacy certification, anonymization result or observed recording behavior.\n\n## Official references\n\n- [Pencil privacy filter](https://developer.axis.com/vapix/network-video/pencil-privacy-filter/) — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/", "url": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Cybersecurity", "item": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "ListItem", "position": 3, "name": "Check the selected Axis pencil filter separately from its settings", "item": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/#article", "identifier": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/", "url": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/", "headline": "Check the selected Axis pencil filter separately from its settings", "description": "Distinguish Axis pencil-filter settings from the selected active filter.", "abstract": "Distinguish Axis pencil-filter settings from the selected active filter. Review the rendered result under an approved privacy requirement without claiming that a visual effect makes people anonymous.", "articleBody": "Bottom line: Record both the settings and the selected filter before assessing the image. Verify the actual output against the owner’s requirement, and keep a successful configuration response separate from privacy acceptance.\nSource fact: documented behavior\nAxis’s Pencil privacy filter describes a monochrome pencil-image effect and exposes separate operations for filter settings, capabilities and selection.\nsetFilterSettings changes the parameters of a filter type, while setSelectedFilter chooses which filter is active.\nThe selection description says none deactivates the filter, and getSelectedFilter reports the current selection.\nWhat the source does not establish\nDo not infer anonymity, legal compliance or coverage of every image consumer from the API’s name. Confirm the actual supported filter and flags. Keep scene visibility, recording, exported images and the owner’s privacy requirement as separately observed acceptance questions.\nApplicability questions\n\nWhich device, filter type and supported flags are actually available?\nWhat current settings and active selection does it report?\nWhich live, recorded or exported paths are within the approved requirement?\nWho may inspect the test images and decide whether the result is acceptable?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends reviewing filter parameters and active selection separately, then assessing each required image path with authorized observers.\n\nObtain the device’s actual capabilities, current settings and selected filter through the supported operations. Record those as separate fields. Ask the privacy and operational owners to define what the resulting image should reveal for the intended task, without replacing that requirement with an unsupported assertion that the filter removes identity.\nPrepare an authorized scene using harmless objects or expressly permitted participants and controlled image access. Set only approved supported parameters, then explicitly inspect the selected-filter result. Do not treat stored settings for a filter type as the evidence that the intended effect is currently selected.\nObserve each approved output path and compare it with the written requirement. Where recordings or exports are part of the scope, inspect those through the normal authorized workflow rather than relying on the live preview. Stop the acceptance if an unreviewed image remains accessible or the operational task cannot be performed, and restore the approved configuration through its supported process.\n\nVerification and evidence\nRetain the capability information, settings, selection readback and restricted observation record for each tested path. Have a reviewer identify which evidence establishes configuration and which establishes the owner’s image requirement. Avoid including identifiable test images in broadly shared tickets or configuration examples.\nUse a proposed desk case containing updated filter settings alongside a selection of none. Ask the reviewer to explain why those records cannot establish an active effect. Keep any privacy or legal assessment with the appropriate owner. This article reports no image test, privacy certification, anonymization result or observed recording behavior.\nOfficial references\n\nPencil privacy filter — Axis Communications; official VAPIX documentation.\n\nSource review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.", "datePublished": "2026-10-29T20:33:23+00:00", "dateModified": "2026-10-29T20:33:34+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/check-the-selected-axis-pencil-filter-separately-from-its-settings/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/physical-security-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Check the selected Axis pencil filter separately from its settings" }, "articleSection": [ "Cybersecurity", "Video Surveillance" ], "keywords": [ "Cybersecurity", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 493, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Axis Communications — Pencil privacy filter", "url": "https://developer.axis.com/vapix/network-video/pencil-privacy-filter/" } } ] } }