<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Appliaction Modeller and attribute with sensitive information in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Appliaction-Modeller-and-attribute-with-sensitive-information/m-p/85040#M36094</link>
    <description>Hello, my name is Met Vonghiran.

&amp;nbsp;

I have&amp;nbsp;2 qustions regarding the application modeller and sensitive information in the application.


	The confirmation of why developer should not use customer's specific information as a spy attribute
	By not logging the input/output/parameter the attribute information will not be outputed to the database


&amp;nbsp;

Development best practice&amp;nbsp;document mentioned that the&amp;nbsp;developer should not use attribute with customer information as a spy attribute due to securtiy reason

I would like to confirm that the reason why&amp;nbsp;those attribute&amp;nbsp;should not be used is that because the information in the attribute will be&amp;nbsp;transfered to the database, hence leaving the customer's specific data in the database could breach the IT security rule.

I have followed the instruction, but would like to confirm that by not using attribute with customer's data and disable the&amp;nbsp;logging function fo&amp;nbsp;the input/output/parameter from those stages, the sensitive information in the attribute will not be outputed to the BP database

&amp;nbsp;

Regards,

Met Vonghiran

&amp;nbsp;

&amp;nbsp;

&amp;nbsp;</description>
    <pubDate>Thu, 05 Apr 2018 06:37:00 GMT</pubDate>
    <dc:creator>MetVonghiran</dc:creator>
    <dc:date>2018-04-05T06:37:00Z</dc:date>
    <item>
      <title>Appliaction Modeller and attribute with sensitive information</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Appliaction-Modeller-and-attribute-with-sensitive-information/m-p/85040#M36094</link>
      <description>Hello, my name is Met Vonghiran.

&amp;nbsp;

I have&amp;nbsp;2 qustions regarding the application modeller and sensitive information in the application.


	The confirmation of why developer should not use customer's specific information as a spy attribute
	By not logging the input/output/parameter the attribute information will not be outputed to the database


&amp;nbsp;

Development best practice&amp;nbsp;document mentioned that the&amp;nbsp;developer should not use attribute with customer information as a spy attribute due to securtiy reason

I would like to confirm that the reason why&amp;nbsp;those attribute&amp;nbsp;should not be used is that because the information in the attribute will be&amp;nbsp;transfered to the database, hence leaving the customer's specific data in the database could breach the IT security rule.

I have followed the instruction, but would like to confirm that by not using attribute with customer's data and disable the&amp;nbsp;logging function fo&amp;nbsp;the input/output/parameter from those stages, the sensitive information in the attribute will not be outputed to the BP database

&amp;nbsp;

Regards,

Met Vonghiran

&amp;nbsp;

&amp;nbsp;

&amp;nbsp;</description>
      <pubDate>Thu, 05 Apr 2018 06:37:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Appliaction-Modeller-and-attribute-with-sensitive-information/m-p/85040#M36094</guid>
      <dc:creator>MetVonghiran</dc:creator>
      <dc:date>2018-04-05T06:37:00Z</dc:date>
    </item>
    <item>
      <title>Yes Met, if sensitive data…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Appliaction-Modeller-and-attribute-with-sensitive-information/m-p/85041#M36095</link>
      <description>Yes Met, if sensitive data is not hardcoded&amp;nbsp;in the model or the diagram, and it's not logged or held in the queue, then it won't be stored in the DB. Aside from security, the other reason to avoid including such data in the model at design-time is that at run-time you'll be working different cases and the chances are the model will fail if hardcoded with customer data.</description>
      <pubDate>Thu, 05 Apr 2018 13:45:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Appliaction-Modeller-and-attribute-with-sensitive-information/m-p/85041#M36095</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2018-04-05T13:45:00Z</dc:date>
    </item>
    <item>
      <title>Thank you so much John…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Appliaction-Modeller-and-attribute-with-sensitive-information/m-p/85042#M36096</link>
      <description>Thank you so much John.
Your input is very clear.
&amp;nbsp;
Regards,
Met Vonghiran</description>
      <pubDate>Fri, 06 Apr 2018 05:42:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Appliaction-Modeller-and-attribute-with-sensitive-information/m-p/85042#M36096</guid>
      <dc:creator>MetVonghiran</dc:creator>
      <dc:date>2018-04-06T05:42:00Z</dc:date>
    </item>
  </channel>
</rss>

