{"id":10029,"date":"2024-10-24T11:03:13","date_gmt":"2024-10-24T15:03:13","guid":{"rendered":"https:\/\/greenstonesystems.com\/?page_id=10029"},"modified":"2025-09-12T12:38:01","modified_gmt":"2025-09-12T16:38:01","slug":"vulnerability-disclosure-policy","status":"publish","type":"page","link":"https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/","title":{"rendered":"Vulnerability Disclosure Policy"},"content":{"rendered":"<p>[et_pb_section fb_built=&#8221;1&#8243; admin_label=&#8221;section&#8221; _builder_version=&#8221;4.27.4&#8243; custom_margin=&#8221;||||false|false&#8221; custom_padding=&#8221;||||false|false&#8221; bottom_divider_style=&#8221;wave2&#8243; bottom_divider_color=&#8221;#443741&#8243; global_colors_info=&#8221;{}&#8221;][et_pb_row admin_label=&#8221;row&#8221; _builder_version=&#8221;4.27.4&#8243; background_size=&#8221;initial&#8221; background_position=&#8221;top_left&#8221; background_repeat=&#8221;repeat&#8221; custom_padding=&#8221;||||false|false&#8221; global_colors_info=&#8221;{}&#8221;][et_pb_column type=&#8221;4_4&#8243; _builder_version=&#8221;4.16&#8243; custom_padding=&#8221;|||&#8221; global_colors_info=&#8221;{}&#8221; custom_padding__hover=&#8221;|||&#8221;][et_pb_text admin_label=&#8221;Text&#8221; _builder_version=&#8221;4.27.4&#8243; text_font=&#8221;&#8211;et_global_body_font||||||||&#8221; text_text_color=&#8221;#443741&#8243; text_font_size=&#8221;16px&#8221; header_text_color=&#8221;#528E30&#8243; header_2_text_color=&#8221;#528E30&#8243; background_size=&#8221;initial&#8221; background_position=&#8221;top_left&#8221; background_repeat=&#8221;repeat&#8221; custom_padding=&#8221;||3em||false|false&#8221; global_colors_info=&#8221;{}&#8221;]<\/p>\n<h1>Vulnerability Disclosure Policy<\/h1>\n<p>&nbsp;<\/p>\n<p><strong>Introduction<\/strong><\/p>\n<p>The purpose of this document is to describe and clarify the Vulnerability Disclosure Policy (VDP) that applies to all domains which Greenstone is responsible for.<\/p>\n<p><strong>1.1 Policy Objective<\/strong><\/p>\n<p>The objective of this policy is to encourage the responsible reporting of suspected vulnerabilities or weaknesses in IT services, systems, resources and\/or processes which may potentially affect Greenstone\u2019s internet-accessible applications.<\/p>\n<p><strong>1.2 Scope and Applicability<\/strong><\/p>\n<p>All systems and services associated with domains listed below are in scope. Likewise, subdomains of each listing, unless explicitly excluded, are always in scope. Additionally, any website published with a link to this policy shall be considered in scope. Vulnerabilities found in non-Greenstone systems from our vendors fall outside of this policy\u2019s scope and should be reported directly to the vendor according to their disclosure policy (if any).<\/p>\n<p>Though we develop and maintain other internet-accessible systems or services, we ask that active research only be conducted on the systems and services covered by the scope of this document. If there is a system not in scope that you think merits inclusion, please contact us to discuss it first. We will increase the scope of this policy over time.<\/p>\n<p><strong>Domains<\/strong><\/p>\n<ul>\n<li>*.greenstonesystems.com<\/li>\n<li>*.agris.com<\/li>\n<li>mygrower.cuturatech.com<\/li>\n<\/ul>\n<p><strong>1.3 Guiding Principles<\/strong><\/p>\n<p>This vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to Greenstone. We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.<\/p>\n<p>We value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures.<\/p>\n<p><strong>2 Policy Specification<\/strong><\/p>\n<p>The following are the minimum set of controls required under this policy.<\/p>\n<p><strong>2.1 Reporting Security Vulnerability<\/strong><\/p>\n<ul>\n<li><strong> Control Objective:<\/strong> Have a clear definition of how to submit a vulnerability report<\/li>\n<li><strong>Control Practice: <\/strong>If you believe you have found a security vulnerability, please submit your report via e-mail to <a href=\"mailto:MySupport@Culturatech.com\">mysupport@culturatech.com<\/a><\/li>\n<\/ul>\n<p><strong>2.2 Required Security Vulnerability Report Details<\/strong><\/p>\n<ul>\n<li><strong>Control Objective:<\/strong> Have a clear definition of the details required in the vulnerability report<\/li>\n<li><strong>Control Practice:<\/strong>\n<ul>\n<li>The website, IP, or page where the vulnerability can be observed<\/li>\n<li>A brief description of the type of vulnerability, e.g. \u201cXSS vulnerability\u201d<\/li>\n<li>Steps to reproduce. These should be benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers<\/li>\n<li>Description of the circumstances, including date(s) and time(s), leading to your reporting of the suspected vulnerability<\/li>\n<li>Where applicable, provide your name, email address and mobile number in the suspected vulnerability report so that we may contact you for clarifications. Please be aware that this information will be passed onto a 3rd party responsible for website development<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>2.3 VDP Participant Expected Behaviour<\/strong><\/p>\n<ul>\n<li><strong>Control Objective:<\/strong> Have a clear definition of the expected behaviour for the VDP participant<\/li>\n<li><strong>Control Practice:<\/strong>\n<ul>\n<li>Do not break any applicable law or regulations<\/li>\n<li>Do not access unnecessary, excessive, or significant amounts of data<\/li>\n<li>Do not modify data in the Organization\u2019s systems or services<\/li>\n<li>Do not use high-intensity invasive or destructive scanning tools to find vulnerabilities<\/li>\n<li>Do not attempt or report any form of denial of service, for example, overwhelming a service with a high volume of requests<\/li>\n<li>Do not submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with \u201cbest practice\u201d, for example missing security headers<\/li>\n<li>Do not submit reports detailing TLS configuration weaknesses, for example \u201cweak\u201d cipher suite support or the presence of TLS1.0 support<\/li>\n<li>Do not communicate any vulnerabilities or associated details other than by means described in this Policy<\/li>\n<li>Do not social engineer, \u2018phish\u2019 or physically attack the Organization\u2019s staff or infrastructure<\/li>\n<li>Do not demand financial compensation to disclose any vulnerabilities<\/li>\n<li>Do not use an exploit to compromise or exfiltrate data, establish command line access and\/or persistence, or use the exploit to \u201cpivot\u201d to<br \/>other systems<\/li>\n<li>Do not intentionally compromise the privacy or safety of Greenstone personnel, or any third parties<\/li>\n<li>Do not intentionally compromise the intellectual property or other commercial or financial interests of any Greenstone personnel or entities, or any third parties<\/li>\n<li>Notify us as soon as possible after you discover a real or potential security issue<\/li>\n<li>Make every effort to avoid privacy violations<\/li>\n<li>Provide us a reasonable amount of time to resolve the issue before you disclose it publicly<\/li>\n<li>Securely delete all data retrieved during your research as soon as it is no longer required<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p><strong>2.4 VDP Submission Expected Response<\/strong><\/p>\n<ul>\n<li><strong>Control Objective:<\/strong> Have a clear definition of the expected response once a vulnerability report has been submitted<\/li>\n<li><strong>Control Practice:<\/strong>\n<ul>\n<li>Once a report has been submitted, Greenstone will respond to the submitter within 5 working days<\/li>\n<li>Greenstone will aim to triage the report within 10 working days<\/li>\n<li>Priority for remediation is assessed by looking at the impact, severity, and exploit complexity<\/li>\n<li>Vulnerability reports might take time to triage or address. You are welcome to enquire on the status but should avoid doing so more than once every 14 days (about 2 weeks)<\/li>\n<li>Greenstone will notify you when the reported vulnerability is remediated<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><span style=\"font-size: 10pt;\">Last update: October, 2024<\/span><\/p>\n<p>[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Vulnerability Disclosure Policy &nbsp; Introduction The purpose of this document is to describe and clarify the Vulnerability Disclosure Policy (VDP) that applies to all domains which Greenstone is responsible for. 1.1 Policy Objective The objective of this policy is to encourage the responsible reporting of suspected vulnerabilities or weaknesses in IT services, systems, resources and\/or [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"[vc_section css=\".vc_custom_1729781684497{margin-top: 3em !important;margin-bottom: 3em !important;}\"][vc_row][vc_column][ultimate_heading main_heading=\"Vulnerability Disclosure Policy\" heading_tag=\"h1\" main_heading_color=\"#69ae62\" alignment=\"left\" margin_design_tab_text=\"\" main_heading_font_family=\"font_family:Poppins|font_call:Poppins|variant:500\" main_heading_style=\"font-weight:500;\"][\/ultimate_heading][vc_column_text]\r\n<h2>Introduction<\/h2>\r\nThe purpose of this document is to describe and clarify the Vulnerability Disclosure Policy (VDP) that applies to all domains which Greenstone is responsible for.\r\n<h3><strong>1.1 Policy Objective<\/strong><\/h3>\r\nThe objective of this policy is to encourage the responsible reporting of suspected vulnerabilities or weaknesses in IT services, systems, resources and\/or processes which may potentially affect Greenstone\u2019s internet-accessible applications.\r\n<h3><strong>1.2 Scope and Applicability<\/strong><\/h3>\r\nAll systems and services associated with domains listed below are in scope. Likewise, subdomains of each listing, unless explicitly excluded, are always in scope. Additionally, any website published with a link to this policy shall be considered in scope. Vulnerabilities found in non-Greenstone systems from our vendors fall outside of this policy\u2019s scope and should be reported directly to the vendor according to their disclosure policy (if any).\r\n\r\nThough we develop and maintain other internet-accessible systems or services, we ask that active research only be conducted on the systems and services covered by the scope of this document. If there is a system not in scope that you think merits inclusion, please contact us to discuss it first. We will increase the scope of this policy over time.\r\n\r\n<strong>Domains<\/strong>\r\n<ul>\r\n \t<li>*.greenstonesystems.com<\/li>\r\n \t<li>*.agris.com<\/li>\r\n \t<li>mygrower.cuturatech.com<\/li>\r\n<\/ul>\r\n<h3><strong>1.3 Guiding Principles<\/strong><\/h3>\r\nThis vulnerability disclosure policy applies to any vulnerabilities you are considering reporting to Greenstone. We recommend reading this vulnerability disclosure policy fully before you report a vulnerability and always acting in compliance with it.\r\n\r\nWe value those who take the time and effort to report security vulnerabilities according to this policy. However, we do not offer monetary rewards for vulnerability disclosures.\r\n<h3><strong>2 Policy Specification<\/strong><\/h3>\r\nThe following are the minimum set of controls required under this policy.\r\n<h3><strong>2.1 Reporting Security Vulnerability<\/strong><\/h3>\r\n<ul>\r\n \t<li><strong> Control Objective:<\/strong> Have a clear definition of how to submit a vulnerability report<\/li>\r\n \t<li><strong>Control Practice: <\/strong>If you believe you have found a security vulnerability, please submit your report via e-mail to <a href=\"mailto:MySupport@Culturatech.com\">MySupport@Culturatech.com<\/a><\/li>\r\n<\/ul>\r\n<h3><strong>2.2 Required Security Vulnerability<\/strong><\/h3>\r\n<ul>\r\n \t<li><strong>Control Objective:<\/strong> Have a clear definition of the details required in the vulnerability report<\/li>\r\n \t<li><strong>Control Practice:<\/strong>\r\n<ul>\r\n \t<li>The website, IP, or page where the vulnerability can be observed<\/li>\r\n \t<li>A brief description of the type of vulnerability e.g., \u201cXSS vulnerability\u201d<\/li>\r\n \t<li>Steps to reproduce. These should be benign, non-destructive, proof of concept. This helps to ensure that the report can be triaged quickly and accurately. It also reduces the likelihood of duplicate reports, or malicious exploitation of some vulnerabilities, such as sub-domain takeovers<\/li>\r\n \t<li>Description of the circumstances, including date(s) and time(s), leading to your reporting of the suspected vulnerability<\/li>\r\n \t<li>Where applicable, provide your name, email address and mobile number in the suspected vulnerability report so that we may contact you for clarifications. Please be aware that this information will be passed onto a 3rd party responsible for website development<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<h3><strong>2.3 VDP Participant Expected Behaviour<\/strong><\/h3>\r\n<ul>\r\n \t<li><strong>Control Objective:<\/strong> Have a clear definition of the expected behaviour for the VDP participant<\/li>\r\n \t<li><strong>Control Practice:<\/strong>\r\n<ul>\r\n \t<li>Do not break any applicable law or regulations<\/li>\r\n \t<li>Do not access unnecessary, excessive, or significant amounts of data<\/li>\r\n \t<li>Do not modify data in the Organization\u2019s systems or services<\/li>\r\n \t<li>Do not use high-intensity invasive or destructive scanning tools to find vulnerabilities<\/li>\r\n \t<li>Do not attempt or report any form of denial of service, for example, overwhelming a service with a high volume of requests<\/li>\r\n \t<li>Do not submit reports detailing non-exploitable vulnerabilities, or reports indicating that the services do not fully align with \u201cbest practice\u201d, for example missing security headers<\/li>\r\n \t<li>Do not submit reports detailing TLS configuration weaknesses, for example \u201cweak\u201d cipher suite support or the presence of TLS1.0 support<\/li>\r\n \t<li>Do not communicate any vulnerabilities or associated details other than by means described in this Policy<\/li>\r\n \t<li>Do not social engineer, \u2018phish\u2019 or physically attack the Organization\u2019s staff or infrastructure<\/li>\r\n \t<li>Do not demand financial compensation to disclose any vulnerabilities<\/li>\r\n \t<li>Do not use an exploit to compromise or exfiltrate data, establish command line access and\/or persistence, or use the exploit to \u201cpivot\u201d to\r\nother systems<\/li>\r\n \t<li>Do not intentionally compromise the privacy or safety of Greenstone personnel, or any third parties<\/li>\r\n \t<li>Do not intentionally compromise the intellectual property or other commercial or financial interests of any Greenstone personnel or entities, or any third parties<\/li>\r\n \t<li>Notify us as soon as possible after you discover a real or potential security issue<\/li>\r\n \t<li>Make every effort to avoid privacy violations<\/li>\r\n \t<li>Provide us a reasonable amount of time to resolve the issue before you disclose it publicly<\/li>\r\n \t<li>Securely delete all data retrieved during your research as soon as it is no longer required<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<h3><strong>2.4 VDP Submission Expected Response<\/strong><\/h3>\r\n<ul>\r\n \t<li><strong>Control Objective:<\/strong> Have a clear definition of the expected response once a vulnerability report has been submitted<\/li>\r\n \t<li><strong>Control Practice:<\/strong>\r\n<ul>\r\n \t<li>Once a report has been submitted, Greenstone will respond to the submitter within 5 working days<\/li>\r\n \t<li>Greenstone will aim to triage the report within 10 working days<\/li>\r\n \t<li>Priority for remediation is assessed by looking at the impact, severity, and exploit complexity<\/li>\r\n \t<li>Vulnerability reports might take time to triage or address. You are welcome to enquire on the status but should avoid doing so more than once every 14 days (about 2 weeks)<\/li>\r\n \t<li>Greenstone will notify you when the reported vulnerability is remediated<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n&nbsp;\r\n\r\n<span style=\"font-size: 10pt;\">Last update: October, 2024<\/span>[\/vc_column_text][\/vc_column][\/vc_row][\/vc_section]","_et_gb_content_width":"","content-type":"","footnotes":""},"class_list":["post-10029","page","type-page","status-publish","hentry"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Vulnerability Disclosure Policy - Greenstone Systems<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Vulnerability Disclosure Policy - Greenstone Systems\" \/>\n<meta property=\"og:description\" content=\"Vulnerability Disclosure Policy &nbsp; Introduction The purpose of this document is to describe and clarify the Vulnerability Disclosure Policy (VDP) that applies to all domains which Greenstone is responsible for. 1.1 Policy Objective The objective of this policy is to encourage the responsible reporting of suspected vulnerabilities or weaknesses in IT services, systems, resources and\/or [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/\" \/>\n<meta property=\"og:site_name\" content=\"Greenstone Systems\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/thinkgreenstone\/\" \/>\n<meta property=\"article:modified_time\" content=\"2025-09-12T16:38:01+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:site\" content=\"@greenstonesys\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/greenstonesystems.com\\\/vulnerability-disclosure-policy\\\/\",\"url\":\"https:\\\/\\\/greenstonesystems.com\\\/vulnerability-disclosure-policy\\\/\",\"name\":\"Vulnerability Disclosure Policy - Greenstone Systems\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/greenstonesystems.com\\\/#website\"},\"datePublished\":\"2024-10-24T15:03:13+00:00\",\"dateModified\":\"2025-09-12T16:38:01+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/greenstonesystems.com\\\/vulnerability-disclosure-policy\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/greenstonesystems.com\\\/vulnerability-disclosure-policy\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/greenstonesystems.com\\\/vulnerability-disclosure-policy\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/greenstonesystems.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Vulnerability Disclosure Policy\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/greenstonesystems.com\\\/#website\",\"url\":\"https:\\\/\\\/greenstonesystems.com\\\/\",\"name\":\"Greenstone Systems\",\"description\":\"Built for Agriculture. Backed by Experience. Powered by Innovation.\",\"publisher\":{\"@id\":\"https:\\\/\\\/greenstonesystems.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/greenstonesystems.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/greenstonesystems.com\\\/#organization\",\"name\":\"Greenstone Systems\",\"url\":\"https:\\\/\\\/greenstonesystems.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/greenstonesystems.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/greenstonesystems.com\\\/wp-content\\\/uploads\\\/2025\\\/10\\\/cropped-stamp-fieldleaf.png\",\"contentUrl\":\"https:\\\/\\\/greenstonesystems.com\\\/wp-content\\\/uploads\\\/2025\\\/10\\\/cropped-stamp-fieldleaf.png\",\"width\":512,\"height\":512,\"caption\":\"Greenstone Systems\"},\"image\":{\"@id\":\"https:\\\/\\\/greenstonesystems.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/thinkgreenstone\\\/\",\"https:\\\/\\\/x.com\\\/greenstonesys\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/greenstone-a-cultura-company\\\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Vulnerability Disclosure Policy - Greenstone Systems","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/","og_locale":"en_US","og_type":"article","og_title":"Vulnerability Disclosure Policy - Greenstone Systems","og_description":"Vulnerability Disclosure Policy &nbsp; Introduction The purpose of this document is to describe and clarify the Vulnerability Disclosure Policy (VDP) that applies to all domains which Greenstone is responsible for. 1.1 Policy Objective The objective of this policy is to encourage the responsible reporting of suspected vulnerabilities or weaknesses in IT services, systems, resources and\/or [&hellip;]","og_url":"https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/","og_site_name":"Greenstone Systems","article_publisher":"https:\/\/www.facebook.com\/thinkgreenstone\/","article_modified_time":"2025-09-12T16:38:01+00:00","twitter_card":"summary_large_image","twitter_site":"@greenstonesys","twitter_misc":{"Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/","url":"https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/","name":"Vulnerability Disclosure Policy - Greenstone Systems","isPartOf":{"@id":"https:\/\/greenstonesystems.com\/#website"},"datePublished":"2024-10-24T15:03:13+00:00","dateModified":"2025-09-12T16:38:01+00:00","breadcrumb":{"@id":"https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/greenstonesystems.com\/vulnerability-disclosure-policy\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/greenstonesystems.com\/"},{"@type":"ListItem","position":2,"name":"Vulnerability Disclosure Policy"}]},{"@type":"WebSite","@id":"https:\/\/greenstonesystems.com\/#website","url":"https:\/\/greenstonesystems.com\/","name":"Greenstone Systems","description":"Built for Agriculture. Backed by Experience. Powered by Innovation.","publisher":{"@id":"https:\/\/greenstonesystems.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/greenstonesystems.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/greenstonesystems.com\/#organization","name":"Greenstone Systems","url":"https:\/\/greenstonesystems.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/greenstonesystems.com\/#\/schema\/logo\/image\/","url":"https:\/\/greenstonesystems.com\/wp-content\/uploads\/2025\/10\/cropped-stamp-fieldleaf.png","contentUrl":"https:\/\/greenstonesystems.com\/wp-content\/uploads\/2025\/10\/cropped-stamp-fieldleaf.png","width":512,"height":512,"caption":"Greenstone Systems"},"image":{"@id":"https:\/\/greenstonesystems.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/thinkgreenstone\/","https:\/\/x.com\/greenstonesys","https:\/\/www.linkedin.com\/company\/greenstone-a-cultura-company\/"]}]}},"_links":{"self":[{"href":"https:\/\/greenstonesystems.com\/wp-json\/wp\/v2\/pages\/10029","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/greenstonesystems.com\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/greenstonesystems.com\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/greenstonesystems.com\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/greenstonesystems.com\/wp-json\/wp\/v2\/comments?post=10029"}],"version-history":[{"count":17,"href":"https:\/\/greenstonesystems.com\/wp-json\/wp\/v2\/pages\/10029\/revisions"}],"predecessor-version":[{"id":85058,"href":"https:\/\/greenstonesystems.com\/wp-json\/wp\/v2\/pages\/10029\/revisions\/85058"}],"wp:attachment":[{"href":"https:\/\/greenstonesystems.com\/wp-json\/wp\/v2\/media?parent=10029"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}