{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/review-axis-automatic-profile-triggers-separately-from-tracking/", "item": { "id": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking/", "slug": "review-axis-automatic-profile-triggers-separately-from-tracking", "url": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking.md", "json": "https://update.dsesecurity.com/api/v1/posts/review-axis-automatic-profile-triggers-separately-from-tracking/" }, "title": "Review Axis automatic profile triggers separately from tracking", "summary": "Review Axis PTZ Autotracker’s automatic-trigger state separately from its selected target. Distinguish automatic zone entry from a client-selected target before accepting operator behavior.", "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": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "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:14+00:00", "modified_at": "2026-10-29T20:33:35+00:00", "reviewed_on": "2026-10-29", "reading_minutes": 3, "word_count": 510, "potentially_affected": "Axis products exposing the documented PTZ Autotracker API interface; confirm actual device, hardware and software applicability before applying the proposed checks.", "dse_recommendation": "DSE recommends recording automatic-trigger mode, selected target and observed camera behavior as distinct client states.", "primary_source": { "name": "Axis Communications — PTZ Autotracker API", "url": "https://developer.axis.com/vapix/network-video/ptz-autotracker-api/", "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: State whether the application should choose a target automatically or await an authorized client selection. Inspect that mode and the target independently before interpreting camera movement or a waiting tracker.

\n

Source fact: documented behavior

\n

Axis’s PTZ Autotracker API defines getAutotrackingState as the state of automatic zone triggering, distinct from getAutotrackingTarget for the tracked object.

\n

The source says automatic mode starts tracking when the first object enters a visible zone; manual mode instead requires a client call to setAutotrackingTarget.

\n

Its target-setting description uses an object identifier to start following and -1 to stop, while the target query uses -1 for no active tracking.

\n

What the source does not establish

\n

Do not infer that manual mode makes all tracking impossible or that an automatic-trigger flag identifies the current object. Confirm the exact application, supported interface and configured zones. This article does not guarantee target selection, detection accuracy, safe camera movement or compatibility with an arbitrary PTZ.

\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 recording automatic-trigger mode, selected target and observed camera behavior as distinct client states.

\n
    \n
  1. Review the actual supported application settings and configured zones with the operator owner. Write the intended manual and automatic behaviors before the pilot. Identify a clear attended movement area and the exact client responsible for any manual target selection, and preserve the approved starting mode.
    2. \n
  2. In the separately authorized automatic case, observe the configured trigger state and a harmless permitted zone entry. Record the target information and actual camera behavior rather than assuming the enabled flag explains every movement. Keep any target that cannot be reconciled with the observation unresolved.
    3. \n
  3. For the approved manual case, explicitly select the permitted visible object through the supported client workflow and retain the actual target identifier. Use the documented target-stop operation when the exercise ends, then inspect the resulting state and camera behavior. Restore the approved trigger mode and operator arrangement without treating a missing target as proof that no other control path exists.
    4. \n
\n

Verification and evidence

\n

Retain application/device identity, relevant zones, automatic-trigger state, target queries, sanitized selection/stop outcomes and the observer’s timeline. Require a reviewer to explain the difference between waiting for a manual choice and a failed automatic trigger. Record the actual stop observation independently from the request response.

\n

Use proposed client fixtures where automatic triggering is disabled but a manual target is selected, and where automatic triggering is enabled without a current target. Require distinct displays and investigation paths for those states. These are planning cases; no tracker, camera movement or stop behavior has been tested for this article.

\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: State whether the application should choose a target automatically or await an authorized client selection. Inspect that mode and the target independently before interpreting camera movement or a waiting tracker.\nSource fact: documented behavior\nAxis’s PTZ Autotracker API defines getAutotrackingState as the state of automatic zone triggering, distinct from getAutotrackingTarget for the tracked object.\nThe source says automatic mode starts tracking when the first object enters a visible zone; manual mode instead requires a client call to setAutotrackingTarget.\nIts target-setting description uses an object identifier to start following and -1 to stop, while the target query uses -1 for no active tracking.\nWhat the source does not establish\nDo not infer that manual mode makes all tracking impossible or that an automatic-trigger flag identifies the current object. Confirm the exact application, supported interface and configured zones. This article does not guarantee target selection, detection accuracy, safe camera movement or compatibility with an arbitrary PTZ.\nApplicability questions\n\nShould zone entry or an authorized client choose the target?\nWhat automatic-trigger state and current target are actually reported?\nWhich visible zone and permitted test object are in scope?\nHow will the operator stop the approved target and restore normal control?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends recording automatic-trigger mode, selected target and observed camera behavior as distinct client states.\n\nReview the actual supported application settings and configured zones with the operator owner. Write the intended manual and automatic behaviors before the pilot. Identify a clear attended movement area and the exact client responsible for any manual target selection, and preserve the approved starting mode.\nIn the separately authorized automatic case, observe the configured trigger state and a harmless permitted zone entry. Record the target information and actual camera behavior rather than assuming the enabled flag explains every movement. Keep any target that cannot be reconciled with the observation unresolved.\nFor the approved manual case, explicitly select the permitted visible object through the supported client workflow and retain the actual target identifier. Use the documented target-stop operation when the exercise ends, then inspect the resulting state and camera behavior. Restore the approved trigger mode and operator arrangement without treating a missing target as proof that no other control path exists.\n\nVerification and evidence\nRetain application/device identity, relevant zones, automatic-trigger state, target queries, sanitized selection/stop outcomes and the observer’s timeline. Require a reviewer to explain the difference between waiting for a manual choice and a failed automatic trigger. Record the actual stop observation independently from the request response.\nUse proposed client fixtures where automatic triggering is disabled but a manual target is selected, and where automatic triggering is enabled without a current target. Require distinct displays and investigation paths for those states. These are planning cases; no tracker, camera movement or stop behavior has been tested for this article.\nOfficial references\n\nPTZ Autotracker API — 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: State whether the application should choose a target automatically or await an authorized client selection. Inspect that mode and the target independently before interpreting camera movement or a waiting tracker.\n\n## Source fact: documented behavior\n\nAxis’s [PTZ Autotracker API](https://developer.axis.com/vapix/network-video/ptz-autotracker-api/) defines getAutotrackingState as the state of automatic zone triggering, distinct from getAutotrackingTarget for the tracked object.\n\nThe source says automatic mode starts tracking when the first object enters a visible zone; manual mode instead requires a client call to setAutotrackingTarget.\n\nIts target-setting description uses an object identifier to start following and -1 to stop, while the target query uses -1 for no active tracking.\n\n## What the source does not establish\n\nDo not infer that manual mode makes all tracking impossible or that an automatic-trigger flag identifies the current object. Confirm the exact application, supported interface and configured zones. This article does not guarantee target selection, detection accuracy, safe camera movement or compatibility with an arbitrary PTZ.\n\n## Applicability questions\n\n- Should zone entry or an authorized client choose the target?\n\n- What automatic-trigger state and current target are actually reported?\n\n- Which visible zone and permitted test object are in scope?\n\n- How will the operator stop the approved target and restore normal control?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends recording automatic-trigger mode, selected target and observed camera behavior as distinct client states.\n\n- Review the actual supported application settings and configured zones with the operator owner. Write the intended manual and automatic behaviors before the pilot. Identify a clear attended movement area and the exact client responsible for any manual target selection, and preserve the approved starting mode.\n\n- In the separately authorized automatic case, observe the configured trigger state and a harmless permitted zone entry. Record the target information and actual camera behavior rather than assuming the enabled flag explains every movement. Keep any target that cannot be reconciled with the observation unresolved.\n\n- For the approved manual case, explicitly select the permitted visible object through the supported client workflow and retain the actual target identifier. Use the documented target-stop operation when the exercise ends, then inspect the resulting state and camera behavior. Restore the approved trigger mode and operator arrangement without treating a missing target as proof that no other control path exists.\n\n## Verification and evidence\n\nRetain application/device identity, relevant zones, automatic-trigger state, target queries, sanitized selection/stop outcomes and the observer’s timeline. Require a reviewer to explain the difference between waiting for a manual choice and a failed automatic trigger. Record the actual stop observation independently from the request response.\n\nUse proposed client fixtures where automatic triggering is disabled but a manual target is selected, and where automatic triggering is enabled without a current target. Require distinct displays and investigation paths for those states. These are planning cases; no tracker, camera movement or stop behavior has been tested for this article.\n\n## Official references\n\n- [PTZ Autotracker API](https://developer.axis.com/vapix/network-video/ptz-autotracker-api/) — 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/review-axis-automatic-profile-triggers-separately-from-tracking/", "url": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-29" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "IT", "item": "https://update.dsesecurity.com/topic/it/" }, { "@type": "ListItem", "position": 3, "name": "Review Axis automatic profile triggers separately from tracking", "item": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking/#article", "identifier": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking/", "url": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking/", "headline": "Review Axis automatic profile triggers separately from tracking", "description": "Review Axis PTZ Autotracker’s automatic-trigger state separately from its selected target.", "abstract": "Review Axis PTZ Autotracker’s automatic-trigger state separately from its selected target. Distinguish automatic zone entry from a client-selected target before accepting operator behavior.", "articleBody": "Bottom line: State whether the application should choose a target automatically or await an authorized client selection. Inspect that mode and the target independently before interpreting camera movement or a waiting tracker.\nSource fact: documented behavior\nAxis’s PTZ Autotracker API defines getAutotrackingState as the state of automatic zone triggering, distinct from getAutotrackingTarget for the tracked object.\nThe source says automatic mode starts tracking when the first object enters a visible zone; manual mode instead requires a client call to setAutotrackingTarget.\nIts target-setting description uses an object identifier to start following and -1 to stop, while the target query uses -1 for no active tracking.\nWhat the source does not establish\nDo not infer that manual mode makes all tracking impossible or that an automatic-trigger flag identifies the current object. Confirm the exact application, supported interface and configured zones. This article does not guarantee target selection, detection accuracy, safe camera movement or compatibility with an arbitrary PTZ.\nApplicability questions\n\nShould zone entry or an authorized client choose the target?\nWhat automatic-trigger state and current target are actually reported?\nWhich visible zone and permitted test object are in scope?\nHow will the operator stop the approved target and restore normal control?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends recording automatic-trigger mode, selected target and observed camera behavior as distinct client states.\n\nReview the actual supported application settings and configured zones with the operator owner. Write the intended manual and automatic behaviors before the pilot. Identify a clear attended movement area and the exact client responsible for any manual target selection, and preserve the approved starting mode.\nIn the separately authorized automatic case, observe the configured trigger state and a harmless permitted zone entry. Record the target information and actual camera behavior rather than assuming the enabled flag explains every movement. Keep any target that cannot be reconciled with the observation unresolved.\nFor the approved manual case, explicitly select the permitted visible object through the supported client workflow and retain the actual target identifier. Use the documented target-stop operation when the exercise ends, then inspect the resulting state and camera behavior. Restore the approved trigger mode and operator arrangement without treating a missing target as proof that no other control path exists.\n\nVerification and evidence\nRetain application/device identity, relevant zones, automatic-trigger state, target queries, sanitized selection/stop outcomes and the observer’s timeline. Require a reviewer to explain the difference between waiting for a manual choice and a failed automatic trigger. Record the actual stop observation independently from the request response.\nUse proposed client fixtures where automatic triggering is disabled but a manual target is selected, and where automatic triggering is enabled without a current target. Require distinct displays and investigation paths for those states. These are planning cases; no tracker, camera movement or stop behavior has been tested for this article.\nOfficial references\n\nPTZ Autotracker API — 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:14+00:00", "dateModified": "2026-10-29T20:33:35+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/review-axis-automatic-profile-triggers-separately-from-tracking/" }, "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/review-axis-automatic-profile-triggers-separately-from-tracking/#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": "Review Axis automatic profile triggers separately from tracking" }, "articleSection": [ "IT", "Video Surveillance" ], "keywords": [ "IT", "Video Surveillance", "Guide", "Advisory priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Video Surveillance", "url": "https://update.dsesecurity.com/topic/video-surveillance/" } ], "wordCount": 510, "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 — PTZ Autotracker API", "url": "https://developer.axis.com/vapix/network-video/ptz-autotracker-api/" } } ] } }