<?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 Re: Output and input control in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/Output-and-input-control/m-p/61677#M4020</link>
    <description>&lt;P&gt;Garbage in/Garbage out.&lt;BR /&gt;&lt;BR /&gt;If you can control what goes into a system, process, storage, function, programme and limit it to correct content/format/you know lineage/it’s traceable you can do a whole lot. But if your not geared for it it’s expensive…&lt;BR /&gt;&lt;BR /&gt;Privacy world data flow mapping is a good example.&lt;BR /&gt;&lt;BR /&gt;Network storage scan what you put in for malware, scan what you take out. clean pipe.&lt;BR /&gt;&lt;BR /&gt;APIs that really control what they accept will stop you getting badly formatted cruft.&lt;BR /&gt;&lt;BR /&gt;You might consider looking at the Biba model which prevents an entity writing to a higher level than allowed to preserve integrity of information at that level / it’s not the same thing but introns where IO can go.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in all cases you’re hoping to control wat good in and what comes out based on classification, type, source, destination - really good example is having applications generate their own SQL queries on the fly so you can cut injection etc off at the source.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Aug 2023 05:44:44 GMT</pubDate>
    <dc:creator>Early_Adopter</dc:creator>
    <dc:date>2023-08-15T05:44:44Z</dc:date>
    <item>
      <title>Output and input control</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Output-and-input-control/m-p/61663#M4019</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;why is output and input controls useful to mitigate data contamination?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From my point of view it has to do something with throughput. So only statement was to mitigate data&amp;nbsp;&lt;SPAN&gt;throughput.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Have someone an idea why it mitigate data contamination.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;OliLue&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Aug 2023 20:28:28 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Output-and-input-control/m-p/61663#M4019</guid>
      <dc:creator>OliLue</dc:creator>
      <dc:date>2023-08-14T20:28:28Z</dc:date>
    </item>
    <item>
      <title>Re: Output and input control</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Output-and-input-control/m-p/61677#M4020</link>
      <description>&lt;P&gt;Garbage in/Garbage out.&lt;BR /&gt;&lt;BR /&gt;If you can control what goes into a system, process, storage, function, programme and limit it to correct content/format/you know lineage/it’s traceable you can do a whole lot. But if your not geared for it it’s expensive…&lt;BR /&gt;&lt;BR /&gt;Privacy world data flow mapping is a good example.&lt;BR /&gt;&lt;BR /&gt;Network storage scan what you put in for malware, scan what you take out. clean pipe.&lt;BR /&gt;&lt;BR /&gt;APIs that really control what they accept will stop you getting badly formatted cruft.&lt;BR /&gt;&lt;BR /&gt;You might consider looking at the Biba model which prevents an entity writing to a higher level than allowed to preserve integrity of information at that level / it’s not the same thing but introns where IO can go.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;in all cases you’re hoping to control wat good in and what comes out based on classification, type, source, destination - really good example is having applications generate their own SQL queries on the fly so you can cut injection etc off at the source.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Aug 2023 05:44:44 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Output-and-input-control/m-p/61677#M4020</guid>
      <dc:creator>Early_Adopter</dc:creator>
      <dc:date>2023-08-15T05:44:44Z</dc:date>
    </item>
    <item>
      <title>Re: Output and input control</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Output-and-input-control/m-p/61695#M4022</link>
      <description>&lt;P&gt;If you examine the OWASP top 10 or SANS top 25 vulnerabilities you'll find some of the common vulnerabilities relate to systems accepting unsanitised input i.e. XSS, SQL injection.&amp;nbsp; Also have a look at Mitre CWE 20.&amp;nbsp; Data can be parsed as code very easily.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In terms of output validation it's always a good idea that there are reasonableness checks of values i.e. is it reasonable that I'm paying several million to a small supplier or individual?&amp;nbsp; Is the data in a field even of the correct format or data type or am I pushing the challenge of validation to a downstream system, which may itself omit any sort of validation.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Aug 2023 15:05:03 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Output-and-input-control/m-p/61695#M4022</guid>
      <dc:creator>Steve-Wilme</dc:creator>
      <dc:date>2023-08-15T15:05:03Z</dc:date>
    </item>
  </channel>
</rss>

