# embeddings_queue

created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 685791f3-caa2-4585-8ee5-beb1843d145d
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 144, "full_page_content": "145 \n \n\u2022 In the case of liquids, gases, or toxins, the absence, presence, or incorrect proportion of a \nvariety of them can be harmful to individuals.  \n\u2022 We can very clearly see how a liquid such as water, in excessive quantities, might be an \nundesirable thing, as we saw in the case of the massive flooding that took place in the southern \nUnited States during Hurricane Katrina in 2005.  \n\u2022 Likewise, the lack of a gas such as oxygen, or too much of the same, can become deadly to \npeople very quickly.  \n\u2022 Although we can see where harm might come from a toxin being introduced to an \nenvironment very clearly, a number of common substances may already be present, but are \nnot toxic in the quantities or mixtures in which they are commonly used.  \n\u2022 We might see certain chemicals as being beneficial when they are used to filter the water in \nour facilities, but the same might not be true if the chemical ratios or mixtures are changed. \nAny variety of living organisms can be dangerous to people, from larger animals, to insects, \nto nearly invisible molds, fungi, or other microscopic organisms.  \n\u2022 People can suffer from contact with living organisms in a variety of ways, from being bitten \nor stung by various critters, to developing breathing problems from inhaling mold.  \n\u2022 Movement can be very harmful to people, particularly when said movement is the result of \nan earthquake, mudslide, avalanche, building structural issue, or other similar problems.  \n\u2022 In most cases, such threats can be both very harmful and very difficult to protect against. \n(c) Safety  \n\u2022 The safety of people is the first and foremost concern on our list when we plan for physical \nsecurity. Safety of people falls above any other concern and must be prioritized above saving \nequipment or data, even when such actions will directly cause such items to be damaged. \n\u2022 We might find an example of this in the fire suppression systems in use in some data centres.  \n\u2022 In many cases, the chemicals, gases, or liquids that are used to extinguish fires in such \nenvironments are very harmful to people and may kill them if used in such an environment.  \n\u2022 For this reason, fire suppression systems are often equipped with a safety override that can \nprevent them from being deployed if there are people in the area.  \n\u2022 If we were to prevent the suppression system from extinguishing the fire because we knew a \nperson was still in the data centre, we might lose all the equipment in the data centre, and \npotentially data that we could not replace.  \n(d) Evacuation \n\u2022 Evacuation is one of the best methods we can use to keep our people safe.", "chunk_id": "9defe0bc-0a55-42f1-8ce5-276ac1e4e248", "chroma:document": "United States during Hurricane Katrina in 2005.  \n\u2022 Likewise, the lack of a gas such as oxygen, or too much of the same, can become deadly to \npeople very quickly.  \n\u2022 Although we can see where harm might come from a toxin being introduced to an \nenvironment very clearly, a number of common substances may already be present, but are"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 7381a549-3d52-46b0-ac54-c83e8a78a95a
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 144, "full_page_content": "145 \n \n\u2022 In the case of liquids, gases, or toxins, the absence, presence, or incorrect proportion of a \nvariety of them can be harmful to individuals.  \n\u2022 We can very clearly see how a liquid such as water, in excessive quantities, might be an \nundesirable thing, as we saw in the case of the massive flooding that took place in the southern \nUnited States during Hurricane Katrina in 2005.  \n\u2022 Likewise, the lack of a gas such as oxygen, or too much of the same, can become deadly to \npeople very quickly.  \n\u2022 Although we can see where harm might come from a toxin being introduced to an \nenvironment very clearly, a number of common substances may already be present, but are \nnot toxic in the quantities or mixtures in which they are commonly used.  \n\u2022 We might see certain chemicals as being beneficial when they are used to filter the water in \nour facilities, but the same might not be true if the chemical ratios or mixtures are changed. \nAny variety of living organisms can be dangerous to people, from larger animals, to insects, \nto nearly invisible molds, fungi, or other microscopic organisms.  \n\u2022 People can suffer from contact with living organisms in a variety of ways, from being bitten \nor stung by various critters, to developing breathing problems from inhaling mold.  \n\u2022 Movement can be very harmful to people, particularly when said movement is the result of \nan earthquake, mudslide, avalanche, building structural issue, or other similar problems.  \n\u2022 In most cases, such threats can be both very harmful and very difficult to protect against. \n(c) Safety  \n\u2022 The safety of people is the first and foremost concern on our list when we plan for physical \nsecurity. Safety of people falls above any other concern and must be prioritized above saving \nequipment or data, even when such actions will directly cause such items to be damaged. \n\u2022 We might find an example of this in the fire suppression systems in use in some data centres.  \n\u2022 In many cases, the chemicals, gases, or liquids that are used to extinguish fires in such \nenvironments are very harmful to people and may kill them if used in such an environment.  \n\u2022 For this reason, fire suppression systems are often equipped with a safety override that can \nprevent them from being deployed if there are people in the area.  \n\u2022 If we were to prevent the suppression system from extinguishing the fire because we knew a \nperson was still in the data centre, we might lose all the equipment in the data centre, and \npotentially data that we could not replace.  \n(d) Evacuation \n\u2022 Evacuation is one of the best methods we can use to keep our people safe.", "chunk_id": "99f0a21c-584e-460a-a5c5-8d6476b9582b", "chroma:document": "not toxic in the quantities or mixtures in which they are commonly used.  \n\u2022 We might see certain chemicals as being beneficial when they are used to filter the water in \nour facilities, but the same might not be true if the chemical ratios or mixtures are changed. \nAny variety of living organisms can be dangerous to people, from larger animals, to insects,"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 8c1e2eee-1918-4bf3-8475-9cd4061c1d05
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 144, "full_page_content": "145 \n \n\u2022 In the case of liquids, gases, or toxins, the absence, presence, or incorrect proportion of a \nvariety of them can be harmful to individuals.  \n\u2022 We can very clearly see how a liquid such as water, in excessive quantities, might be an \nundesirable thing, as we saw in the case of the massive flooding that took place in the southern \nUnited States during Hurricane Katrina in 2005.  \n\u2022 Likewise, the lack of a gas such as oxygen, or too much of the same, can become deadly to \npeople very quickly.  \n\u2022 Although we can see where harm might come from a toxin being introduced to an \nenvironment very clearly, a number of common substances may already be present, but are \nnot toxic in the quantities or mixtures in which they are commonly used.  \n\u2022 We might see certain chemicals as being beneficial when they are used to filter the water in \nour facilities, but the same might not be true if the chemical ratios or mixtures are changed. \nAny variety of living organisms can be dangerous to people, from larger animals, to insects, \nto nearly invisible molds, fungi, or other microscopic organisms.  \n\u2022 People can suffer from contact with living organisms in a variety of ways, from being bitten \nor stung by various critters, to developing breathing problems from inhaling mold.  \n\u2022 Movement can be very harmful to people, particularly when said movement is the result of \nan earthquake, mudslide, avalanche, building structural issue, or other similar problems.  \n\u2022 In most cases, such threats can be both very harmful and very difficult to protect against. \n(c) Safety  \n\u2022 The safety of people is the first and foremost concern on our list when we plan for physical \nsecurity. Safety of people falls above any other concern and must be prioritized above saving \nequipment or data, even when such actions will directly cause such items to be damaged. \n\u2022 We might find an example of this in the fire suppression systems in use in some data centres.  \n\u2022 In many cases, the chemicals, gases, or liquids that are used to extinguish fires in such \nenvironments are very harmful to people and may kill them if used in such an environment.  \n\u2022 For this reason, fire suppression systems are often equipped with a safety override that can \nprevent them from being deployed if there are people in the area.  \n\u2022 If we were to prevent the suppression system from extinguishing the fire because we knew a \nperson was still in the data centre, we might lose all the equipment in the data centre, and \npotentially data that we could not replace.  \n(d) Evacuation \n\u2022 Evacuation is one of the best methods we can use to keep our people safe.", "chunk_id": "661e855c-d866-4d8a-ba9a-dc3d3b5854a1", "chroma:document": "to nearly invisible molds, fungi, or other microscopic organisms.  \n\u2022 People can suffer from contact with living organisms in a variety of ways, from being bitten \nor stung by various critters, to developing breathing problems from inhaling mold.  \n\u2022 Movement can be very harmful to people, particularly when said movement is the result of"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: aa887b73-607a-4a1b-bfdd-424b730006a9
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 144, "full_page_content": "145 \n \n\u2022 In the case of liquids, gases, or toxins, the absence, presence, or incorrect proportion of a \nvariety of them can be harmful to individuals.  \n\u2022 We can very clearly see how a liquid such as water, in excessive quantities, might be an \nundesirable thing, as we saw in the case of the massive flooding that took place in the southern \nUnited States during Hurricane Katrina in 2005.  \n\u2022 Likewise, the lack of a gas such as oxygen, or too much of the same, can become deadly to \npeople very quickly.  \n\u2022 Although we can see where harm might come from a toxin being introduced to an \nenvironment very clearly, a number of common substances may already be present, but are \nnot toxic in the quantities or mixtures in which they are commonly used.  \n\u2022 We might see certain chemicals as being beneficial when they are used to filter the water in \nour facilities, but the same might not be true if the chemical ratios or mixtures are changed. \nAny variety of living organisms can be dangerous to people, from larger animals, to insects, \nto nearly invisible molds, fungi, or other microscopic organisms.  \n\u2022 People can suffer from contact with living organisms in a variety of ways, from being bitten \nor stung by various critters, to developing breathing problems from inhaling mold.  \n\u2022 Movement can be very harmful to people, particularly when said movement is the result of \nan earthquake, mudslide, avalanche, building structural issue, or other similar problems.  \n\u2022 In most cases, such threats can be both very harmful and very difficult to protect against. \n(c) Safety  \n\u2022 The safety of people is the first and foremost concern on our list when we plan for physical \nsecurity. Safety of people falls above any other concern and must be prioritized above saving \nequipment or data, even when such actions will directly cause such items to be damaged. \n\u2022 We might find an example of this in the fire suppression systems in use in some data centres.  \n\u2022 In many cases, the chemicals, gases, or liquids that are used to extinguish fires in such \nenvironments are very harmful to people and may kill them if used in such an environment.  \n\u2022 For this reason, fire suppression systems are often equipped with a safety override that can \nprevent them from being deployed if there are people in the area.  \n\u2022 If we were to prevent the suppression system from extinguishing the fire because we knew a \nperson was still in the data centre, we might lose all the equipment in the data centre, and \npotentially data that we could not replace.  \n(d) Evacuation \n\u2022 Evacuation is one of the best methods we can use to keep our people safe.", "chunk_id": "09ec0ef9-a032-4cd3-bdeb-38a91d7cc1f5", "chroma:document": "an earthquake, mudslide, avalanche, building structural issue, or other similar problems.  \n\u2022 In most cases, such threats can be both very harmful and very difficult to protect against. \n(c) Safety  \n\u2022 The safety of people is the first and foremost concern on our list when we plan for physical"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: e682dee4-48c7-4757-a49f-45ba46fb15be
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 144, "full_page_content": "145 \n \n\u2022 In the case of liquids, gases, or toxins, the absence, presence, or incorrect proportion of a \nvariety of them can be harmful to individuals.  \n\u2022 We can very clearly see how a liquid such as water, in excessive quantities, might be an \nundesirable thing, as we saw in the case of the massive flooding that took place in the southern \nUnited States during Hurricane Katrina in 2005.  \n\u2022 Likewise, the lack of a gas such as oxygen, or too much of the same, can become deadly to \npeople very quickly.  \n\u2022 Although we can see where harm might come from a toxin being introduced to an \nenvironment very clearly, a number of common substances may already be present, but are \nnot toxic in the quantities or mixtures in which they are commonly used.  \n\u2022 We might see certain chemicals as being beneficial when they are used to filter the water in \nour facilities, but the same might not be true if the chemical ratios or mixtures are changed. \nAny variety of living organisms can be dangerous to people, from larger animals, to insects, \nto nearly invisible molds, fungi, or other microscopic organisms.  \n\u2022 People can suffer from contact with living organisms in a variety of ways, from being bitten \nor stung by various critters, to developing breathing problems from inhaling mold.  \n\u2022 Movement can be very harmful to people, particularly when said movement is the result of \nan earthquake, mudslide, avalanche, building structural issue, or other similar problems.  \n\u2022 In most cases, such threats can be both very harmful and very difficult to protect against. \n(c) Safety  \n\u2022 The safety of people is the first and foremost concern on our list when we plan for physical \nsecurity. Safety of people falls above any other concern and must be prioritized above saving \nequipment or data, even when such actions will directly cause such items to be damaged. \n\u2022 We might find an example of this in the fire suppression systems in use in some data centres.  \n\u2022 In many cases, the chemicals, gases, or liquids that are used to extinguish fires in such \nenvironments are very harmful to people and may kill them if used in such an environment.  \n\u2022 For this reason, fire suppression systems are often equipped with a safety override that can \nprevent them from being deployed if there are people in the area.  \n\u2022 If we were to prevent the suppression system from extinguishing the fire because we knew a \nperson was still in the data centre, we might lose all the equipment in the data centre, and \npotentially data that we could not replace.  \n(d) Evacuation \n\u2022 Evacuation is one of the best methods we can use to keep our people safe.", "chunk_id": "f51b738d-15eb-4d75-8241-df09dc71ec77", "chroma:document": "security. Safety of people falls above any other concern and must be prioritized above saving \nequipment or data, even when such actions will directly cause such items to be damaged. \n\u2022 We might find an example of this in the fire suppression systems in use in some data centres.  \n\u2022 In many cases, the chemicals, gases, or liquids that are used to extinguish fires in such"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 6770a170-5496-4406-8398-b0d94e87d056
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 144, "full_page_content": "145 \n \n\u2022 In the case of liquids, gases, or toxins, the absence, presence, or incorrect proportion of a \nvariety of them can be harmful to individuals.  \n\u2022 We can very clearly see how a liquid such as water, in excessive quantities, might be an \nundesirable thing, as we saw in the case of the massive flooding that took place in the southern \nUnited States during Hurricane Katrina in 2005.  \n\u2022 Likewise, the lack of a gas such as oxygen, or too much of the same, can become deadly to \npeople very quickly.  \n\u2022 Although we can see where harm might come from a toxin being introduced to an \nenvironment very clearly, a number of common substances may already be present, but are \nnot toxic in the quantities or mixtures in which they are commonly used.  \n\u2022 We might see certain chemicals as being beneficial when they are used to filter the water in \nour facilities, but the same might not be true if the chemical ratios or mixtures are changed. \nAny variety of living organisms can be dangerous to people, from larger animals, to insects, \nto nearly invisible molds, fungi, or other microscopic organisms.  \n\u2022 People can suffer from contact with living organisms in a variety of ways, from being bitten \nor stung by various critters, to developing breathing problems from inhaling mold.  \n\u2022 Movement can be very harmful to people, particularly when said movement is the result of \nan earthquake, mudslide, avalanche, building structural issue, or other similar problems.  \n\u2022 In most cases, such threats can be both very harmful and very difficult to protect against. \n(c) Safety  \n\u2022 The safety of people is the first and foremost concern on our list when we plan for physical \nsecurity. Safety of people falls above any other concern and must be prioritized above saving \nequipment or data, even when such actions will directly cause such items to be damaged. \n\u2022 We might find an example of this in the fire suppression systems in use in some data centres.  \n\u2022 In many cases, the chemicals, gases, or liquids that are used to extinguish fires in such \nenvironments are very harmful to people and may kill them if used in such an environment.  \n\u2022 For this reason, fire suppression systems are often equipped with a safety override that can \nprevent them from being deployed if there are people in the area.  \n\u2022 If we were to prevent the suppression system from extinguishing the fire because we knew a \nperson was still in the data centre, we might lose all the equipment in the data centre, and \npotentially data that we could not replace.  \n(d) Evacuation \n\u2022 Evacuation is one of the best methods we can use to keep our people safe.", "chunk_id": "6c3f195f-4659-4a6d-b7fa-12b4a7e9aa10", "chroma:document": "environments are very harmful to people and may kill them if used in such an environment.  \n\u2022 For this reason, fire suppression systems are often equipped with a safety override that can \nprevent them from being deployed if there are people in the area.  \n\u2022 If we were to prevent the suppression system from extinguishing the fire because we knew a"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 71a19f67-ac6a-4c43-879e-182fd37770da
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 144, "full_page_content": "145 \n \n\u2022 In the case of liquids, gases, or toxins, the absence, presence, or incorrect proportion of a \nvariety of them can be harmful to individuals.  \n\u2022 We can very clearly see how a liquid such as water, in excessive quantities, might be an \nundesirable thing, as we saw in the case of the massive flooding that took place in the southern \nUnited States during Hurricane Katrina in 2005.  \n\u2022 Likewise, the lack of a gas such as oxygen, or too much of the same, can become deadly to \npeople very quickly.  \n\u2022 Although we can see where harm might come from a toxin being introduced to an \nenvironment very clearly, a number of common substances may already be present, but are \nnot toxic in the quantities or mixtures in which they are commonly used.  \n\u2022 We might see certain chemicals as being beneficial when they are used to filter the water in \nour facilities, but the same might not be true if the chemical ratios or mixtures are changed. \nAny variety of living organisms can be dangerous to people, from larger animals, to insects, \nto nearly invisible molds, fungi, or other microscopic organisms.  \n\u2022 People can suffer from contact with living organisms in a variety of ways, from being bitten \nor stung by various critters, to developing breathing problems from inhaling mold.  \n\u2022 Movement can be very harmful to people, particularly when said movement is the result of \nan earthquake, mudslide, avalanche, building structural issue, or other similar problems.  \n\u2022 In most cases, such threats can be both very harmful and very difficult to protect against. \n(c) Safety  \n\u2022 The safety of people is the first and foremost concern on our list when we plan for physical \nsecurity. Safety of people falls above any other concern and must be prioritized above saving \nequipment or data, even when such actions will directly cause such items to be damaged. \n\u2022 We might find an example of this in the fire suppression systems in use in some data centres.  \n\u2022 In many cases, the chemicals, gases, or liquids that are used to extinguish fires in such \nenvironments are very harmful to people and may kill them if used in such an environment.  \n\u2022 For this reason, fire suppression systems are often equipped with a safety override that can \nprevent them from being deployed if there are people in the area.  \n\u2022 If we were to prevent the suppression system from extinguishing the fire because we knew a \nperson was still in the data centre, we might lose all the equipment in the data centre, and \npotentially data that we could not replace.  \n(d) Evacuation \n\u2022 Evacuation is one of the best methods we can use to keep our people safe.", "chunk_id": "b686046f-bafe-426f-8cba-4cf32ddc2642", "chroma:document": "person was still in the data centre, we might lose all the equipment in the data centre, and \npotentially data that we could not replace.  \n(d) Evacuation \n\u2022 Evacuation is one of the best methods we can use to keep our people safe."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 80d679dc-7f39-4e23-be61-1e0db83bfa9e
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 145, "full_page_content": "146 \n \n\u2022 In almost any dangerous situation, an orderly evacuation away from the source of danger is \nthe best thing we can do.  \n\u2022 There are a few main principles to consider when planning an evacuation: where, how, and \nwho.  \n(i) Where \n\u2022 Where we will be evacuating to is an important piece of information to consider in advance, \nwhether we are evacuating a commercial building or a residence.  \n\u2022 We need to get everyone to the same place to ensure that they are at a safe distance and that \nwe can account for everyone.  \n\u2022 If we do not do this in an orderly and consistent fashion, we may end up with a variety of \nissues. In commercial buildings, evacuation meeting places are often marked with signs, and \non evacuation maps. \n(ii) How  \n\u2022 Also of importance is the route we will follow to reach the evacuation meeting place. When \nplanning such routes, we should consider where the nearest exit from a given area can be \nreached, as well as alternate routes if some routes are impassable in an emergency.  \n\u2022 We should also avoid the use of areas that are dangerous or unusable in emergencies, such as \nelevators or areas that might be blocked by automatically closing fire doors. \n(iii) Who  \n\u2022 The most vital portion of the evacuation, of course, is to ensure that we actually get everyone \nout of the building, and that we can account for everyone at the evacuation meeting place. \n\u2022 This process typically requires at least two people to be responsible for any given group of \npeople: one person to ensure that everyone he or she is responsible for has actually left the \nbuilding and another at the meeting place to ensure that everyone has arrived safely.  \n(iv) Practice  \n\u2022 Particularly in large facilities, a full evacuation can be a complicated prospect. In a true \nemergency, if we do not evacuate quickly and properly, a great number of lives may be lost.  \n\u2022 As an unfortunate attestation to this, we can look to the example of the 2001 attacks on the \nWorld Trade Center in the United States.  \n\u2022 A study conducted in 2008 determined that only 8.6 percent of the people in the buildings \nactually evacuated when the alarms were sounded. The rest remained in the buildings, \ngathering belongings, shutting down computers, and performing other such tasks. It is", "chunk_id": "4a199dbc-ebed-4e43-b4f4-760f46b99f02", "chroma:document": "146 \n \n\u2022 In almost any dangerous situation, an orderly evacuation away from the source of danger is \nthe best thing we can do.  \n\u2022 There are a few main principles to consider when planning an evacuation: where, how, and \nwho.  \n(i) Where \n\u2022 Where we will be evacuating to is an important piece of information to consider in advance,"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 29090b6e-eb88-404a-91de-4307b44bd470
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 145, "full_page_content": "146 \n \n\u2022 In almost any dangerous situation, an orderly evacuation away from the source of danger is \nthe best thing we can do.  \n\u2022 There are a few main principles to consider when planning an evacuation: where, how, and \nwho.  \n(i) Where \n\u2022 Where we will be evacuating to is an important piece of information to consider in advance, \nwhether we are evacuating a commercial building or a residence.  \n\u2022 We need to get everyone to the same place to ensure that they are at a safe distance and that \nwe can account for everyone.  \n\u2022 If we do not do this in an orderly and consistent fashion, we may end up with a variety of \nissues. In commercial buildings, evacuation meeting places are often marked with signs, and \non evacuation maps. \n(ii) How  \n\u2022 Also of importance is the route we will follow to reach the evacuation meeting place. When \nplanning such routes, we should consider where the nearest exit from a given area can be \nreached, as well as alternate routes if some routes are impassable in an emergency.  \n\u2022 We should also avoid the use of areas that are dangerous or unusable in emergencies, such as \nelevators or areas that might be blocked by automatically closing fire doors. \n(iii) Who  \n\u2022 The most vital portion of the evacuation, of course, is to ensure that we actually get everyone \nout of the building, and that we can account for everyone at the evacuation meeting place. \n\u2022 This process typically requires at least two people to be responsible for any given group of \npeople: one person to ensure that everyone he or she is responsible for has actually left the \nbuilding and another at the meeting place to ensure that everyone has arrived safely.  \n(iv) Practice  \n\u2022 Particularly in large facilities, a full evacuation can be a complicated prospect. In a true \nemergency, if we do not evacuate quickly and properly, a great number of lives may be lost.  \n\u2022 As an unfortunate attestation to this, we can look to the example of the 2001 attacks on the \nWorld Trade Center in the United States.  \n\u2022 A study conducted in 2008 determined that only 8.6 percent of the people in the buildings \nactually evacuated when the alarms were sounded. The rest remained in the buildings, \ngathering belongings, shutting down computers, and performing other such tasks. It is", "chunk_id": "56d8be66-ec5e-48e8-8459-082575fa1a20", "chroma:document": "whether we are evacuating a commercial building or a residence.  \n\u2022 We need to get everyone to the same place to ensure that they are at a safe distance and that \nwe can account for everyone.  \n\u2022 If we do not do this in an orderly and consistent fashion, we may end up with a variety of \nissues. In commercial buildings, evacuation meeting places are often marked with signs, and"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: bf538106-bfa4-45d5-affc-27a0341e174f
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 145, "full_page_content": "146 \n \n\u2022 In almost any dangerous situation, an orderly evacuation away from the source of danger is \nthe best thing we can do.  \n\u2022 There are a few main principles to consider when planning an evacuation: where, how, and \nwho.  \n(i) Where \n\u2022 Where we will be evacuating to is an important piece of information to consider in advance, \nwhether we are evacuating a commercial building or a residence.  \n\u2022 We need to get everyone to the same place to ensure that they are at a safe distance and that \nwe can account for everyone.  \n\u2022 If we do not do this in an orderly and consistent fashion, we may end up with a variety of \nissues. In commercial buildings, evacuation meeting places are often marked with signs, and \non evacuation maps. \n(ii) How  \n\u2022 Also of importance is the route we will follow to reach the evacuation meeting place. When \nplanning such routes, we should consider where the nearest exit from a given area can be \nreached, as well as alternate routes if some routes are impassable in an emergency.  \n\u2022 We should also avoid the use of areas that are dangerous or unusable in emergencies, such as \nelevators or areas that might be blocked by automatically closing fire doors. \n(iii) Who  \n\u2022 The most vital portion of the evacuation, of course, is to ensure that we actually get everyone \nout of the building, and that we can account for everyone at the evacuation meeting place. \n\u2022 This process typically requires at least two people to be responsible for any given group of \npeople: one person to ensure that everyone he or she is responsible for has actually left the \nbuilding and another at the meeting place to ensure that everyone has arrived safely.  \n(iv) Practice  \n\u2022 Particularly in large facilities, a full evacuation can be a complicated prospect. In a true \nemergency, if we do not evacuate quickly and properly, a great number of lives may be lost.  \n\u2022 As an unfortunate attestation to this, we can look to the example of the 2001 attacks on the \nWorld Trade Center in the United States.  \n\u2022 A study conducted in 2008 determined that only 8.6 percent of the people in the buildings \nactually evacuated when the alarms were sounded. The rest remained in the buildings, \ngathering belongings, shutting down computers, and performing other such tasks. It is", "chunk_id": "4640f26c-db3d-4c90-a122-f5cfdd0e3e18", "chroma:document": "on evacuation maps. \n(ii) How  \n\u2022 Also of importance is the route we will follow to reach the evacuation meeting place. When \nplanning such routes, we should consider where the nearest exit from a given area can be \nreached, as well as alternate routes if some routes are impassable in an emergency."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: f4272a35-f585-4e10-85f8-63eca63f2d57
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 145, "full_page_content": "146 \n \n\u2022 In almost any dangerous situation, an orderly evacuation away from the source of danger is \nthe best thing we can do.  \n\u2022 There are a few main principles to consider when planning an evacuation: where, how, and \nwho.  \n(i) Where \n\u2022 Where we will be evacuating to is an important piece of information to consider in advance, \nwhether we are evacuating a commercial building or a residence.  \n\u2022 We need to get everyone to the same place to ensure that they are at a safe distance and that \nwe can account for everyone.  \n\u2022 If we do not do this in an orderly and consistent fashion, we may end up with a variety of \nissues. In commercial buildings, evacuation meeting places are often marked with signs, and \non evacuation maps. \n(ii) How  \n\u2022 Also of importance is the route we will follow to reach the evacuation meeting place. When \nplanning such routes, we should consider where the nearest exit from a given area can be \nreached, as well as alternate routes if some routes are impassable in an emergency.  \n\u2022 We should also avoid the use of areas that are dangerous or unusable in emergencies, such as \nelevators or areas that might be blocked by automatically closing fire doors. \n(iii) Who  \n\u2022 The most vital portion of the evacuation, of course, is to ensure that we actually get everyone \nout of the building, and that we can account for everyone at the evacuation meeting place. \n\u2022 This process typically requires at least two people to be responsible for any given group of \npeople: one person to ensure that everyone he or she is responsible for has actually left the \nbuilding and another at the meeting place to ensure that everyone has arrived safely.  \n(iv) Practice  \n\u2022 Particularly in large facilities, a full evacuation can be a complicated prospect. In a true \nemergency, if we do not evacuate quickly and properly, a great number of lives may be lost.  \n\u2022 As an unfortunate attestation to this, we can look to the example of the 2001 attacks on the \nWorld Trade Center in the United States.  \n\u2022 A study conducted in 2008 determined that only 8.6 percent of the people in the buildings \nactually evacuated when the alarms were sounded. The rest remained in the buildings, \ngathering belongings, shutting down computers, and performing other such tasks. It is", "chunk_id": "2b99240b-f3f1-4f2b-be85-3f9b8f5aae85", "chroma:document": "\u2022 We should also avoid the use of areas that are dangerous or unusable in emergencies, such as \nelevators or areas that might be blocked by automatically closing fire doors. \n(iii) Who  \n\u2022 The most vital portion of the evacuation, of course, is to ensure that we actually get everyone \nout of the building, and that we can account for everyone at the evacuation meeting place."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 302e44f2-8ec3-4015-980a-41510319076b
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 145, "full_page_content": "146 \n \n\u2022 In almost any dangerous situation, an orderly evacuation away from the source of danger is \nthe best thing we can do.  \n\u2022 There are a few main principles to consider when planning an evacuation: where, how, and \nwho.  \n(i) Where \n\u2022 Where we will be evacuating to is an important piece of information to consider in advance, \nwhether we are evacuating a commercial building or a residence.  \n\u2022 We need to get everyone to the same place to ensure that they are at a safe distance and that \nwe can account for everyone.  \n\u2022 If we do not do this in an orderly and consistent fashion, we may end up with a variety of \nissues. In commercial buildings, evacuation meeting places are often marked with signs, and \non evacuation maps. \n(ii) How  \n\u2022 Also of importance is the route we will follow to reach the evacuation meeting place. When \nplanning such routes, we should consider where the nearest exit from a given area can be \nreached, as well as alternate routes if some routes are impassable in an emergency.  \n\u2022 We should also avoid the use of areas that are dangerous or unusable in emergencies, such as \nelevators or areas that might be blocked by automatically closing fire doors. \n(iii) Who  \n\u2022 The most vital portion of the evacuation, of course, is to ensure that we actually get everyone \nout of the building, and that we can account for everyone at the evacuation meeting place. \n\u2022 This process typically requires at least two people to be responsible for any given group of \npeople: one person to ensure that everyone he or she is responsible for has actually left the \nbuilding and another at the meeting place to ensure that everyone has arrived safely.  \n(iv) Practice  \n\u2022 Particularly in large facilities, a full evacuation can be a complicated prospect. In a true \nemergency, if we do not evacuate quickly and properly, a great number of lives may be lost.  \n\u2022 As an unfortunate attestation to this, we can look to the example of the 2001 attacks on the \nWorld Trade Center in the United States.  \n\u2022 A study conducted in 2008 determined that only 8.6 percent of the people in the buildings \nactually evacuated when the alarms were sounded. The rest remained in the buildings, \ngathering belongings, shutting down computers, and performing other such tasks. It is", "chunk_id": "8631370d-a60e-4529-8d1e-c18497eeb6ea", "chroma:document": "\u2022 This process typically requires at least two people to be responsible for any given group of \npeople: one person to ensure that everyone he or she is responsible for has actually left the \nbuilding and another at the meeting place to ensure that everyone has arrived safely.  \n(iv) Practice"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 632dd7f0-182f-493f-ae4b-a3843e4a494a
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 145, "full_page_content": "146 \n \n\u2022 In almost any dangerous situation, an orderly evacuation away from the source of danger is \nthe best thing we can do.  \n\u2022 There are a few main principles to consider when planning an evacuation: where, how, and \nwho.  \n(i) Where \n\u2022 Where we will be evacuating to is an important piece of information to consider in advance, \nwhether we are evacuating a commercial building or a residence.  \n\u2022 We need to get everyone to the same place to ensure that they are at a safe distance and that \nwe can account for everyone.  \n\u2022 If we do not do this in an orderly and consistent fashion, we may end up with a variety of \nissues. In commercial buildings, evacuation meeting places are often marked with signs, and \non evacuation maps. \n(ii) How  \n\u2022 Also of importance is the route we will follow to reach the evacuation meeting place. When \nplanning such routes, we should consider where the nearest exit from a given area can be \nreached, as well as alternate routes if some routes are impassable in an emergency.  \n\u2022 We should also avoid the use of areas that are dangerous or unusable in emergencies, such as \nelevators or areas that might be blocked by automatically closing fire doors. \n(iii) Who  \n\u2022 The most vital portion of the evacuation, of course, is to ensure that we actually get everyone \nout of the building, and that we can account for everyone at the evacuation meeting place. \n\u2022 This process typically requires at least two people to be responsible for any given group of \npeople: one person to ensure that everyone he or she is responsible for has actually left the \nbuilding and another at the meeting place to ensure that everyone has arrived safely.  \n(iv) Practice  \n\u2022 Particularly in large facilities, a full evacuation can be a complicated prospect. In a true \nemergency, if we do not evacuate quickly and properly, a great number of lives may be lost.  \n\u2022 As an unfortunate attestation to this, we can look to the example of the 2001 attacks on the \nWorld Trade Center in the United States.  \n\u2022 A study conducted in 2008 determined that only 8.6 percent of the people in the buildings \nactually evacuated when the alarms were sounded. The rest remained in the buildings, \ngathering belongings, shutting down computers, and performing other such tasks. It is", "chunk_id": "6203cc2b-3495-453b-a2d5-b091dbfa8593", "chroma:document": "(iv) Practice  \n\u2022 Particularly in large facilities, a full evacuation can be a complicated prospect. In a true \nemergency, if we do not evacuate quickly and properly, a great number of lives may be lost.  \n\u2022 As an unfortunate attestation to this, we can look to the example of the 2001 attacks on the \nWorld Trade Center in the United States."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 801f20de-17cd-45ba-b9b4-3b9cc842287e
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 145, "full_page_content": "146 \n \n\u2022 In almost any dangerous situation, an orderly evacuation away from the source of danger is \nthe best thing we can do.  \n\u2022 There are a few main principles to consider when planning an evacuation: where, how, and \nwho.  \n(i) Where \n\u2022 Where we will be evacuating to is an important piece of information to consider in advance, \nwhether we are evacuating a commercial building or a residence.  \n\u2022 We need to get everyone to the same place to ensure that they are at a safe distance and that \nwe can account for everyone.  \n\u2022 If we do not do this in an orderly and consistent fashion, we may end up with a variety of \nissues. In commercial buildings, evacuation meeting places are often marked with signs, and \non evacuation maps. \n(ii) How  \n\u2022 Also of importance is the route we will follow to reach the evacuation meeting place. When \nplanning such routes, we should consider where the nearest exit from a given area can be \nreached, as well as alternate routes if some routes are impassable in an emergency.  \n\u2022 We should also avoid the use of areas that are dangerous or unusable in emergencies, such as \nelevators or areas that might be blocked by automatically closing fire doors. \n(iii) Who  \n\u2022 The most vital portion of the evacuation, of course, is to ensure that we actually get everyone \nout of the building, and that we can account for everyone at the evacuation meeting place. \n\u2022 This process typically requires at least two people to be responsible for any given group of \npeople: one person to ensure that everyone he or she is responsible for has actually left the \nbuilding and another at the meeting place to ensure that everyone has arrived safely.  \n(iv) Practice  \n\u2022 Particularly in large facilities, a full evacuation can be a complicated prospect. In a true \nemergency, if we do not evacuate quickly and properly, a great number of lives may be lost.  \n\u2022 As an unfortunate attestation to this, we can look to the example of the 2001 attacks on the \nWorld Trade Center in the United States.  \n\u2022 A study conducted in 2008 determined that only 8.6 percent of the people in the buildings \nactually evacuated when the alarms were sounded. The rest remained in the buildings, \ngathering belongings, shutting down computers, and performing other such tasks. It is", "chunk_id": "a9814437-3679-4786-986d-b33eb2c1117b", "chroma:document": "\u2022 A study conducted in 2008 determined that only 8.6 percent of the people in the buildings \nactually evacuated when the alarms were sounded. The rest remained in the buildings, \ngathering belongings, shutting down computers, and performing other such tasks. It is"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 2b4d4859-53e4-4157-baa6-fc21897c9d38
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 146, "full_page_content": "147 \n \nimportant that we train our personnel to evacuate safely, and to respond quickly and properly \nwhen the signal to evacuate has been given. \n(e) Administrative Controls \n\u2022 We may, and likely will, also have a variety of administrative controls in place to protect \npeople, in addition to the physical measures we put in place.  \n\u2022 Administrative controls are usually based on rules of some variety.  \n\u2022 More specifically, they may be policies, procedures, guidelines, regulations, laws, or similar \nbodies, and may be instituted at any level from informal company policies to federal laws.  \n\u2022 Companies put several common practices in place specifically to protect our people and our \ninterests in general. One of the most common is the background check.  \n\u2022 When an individual has made it far enough through the hiring process that it seems likely he \nor she will be hired, the hiring company will often institute a background check.  \n\u2022 A number of companies globally carry out such background checks, including AccuScreen \nand LexisNexis.  \n\u2022 Such investigations will typically involve checks for criminal history, verification of previous \nemployment, verification of education, credit checks, drug testing, and other items, depending \non the position being pursued.  \n\u2022 We may also conduct a variety of reoccurring checks on those in our employ.  \n\u2022 One of the more common and well-known examples can be seen in the drug tests conducted \nby certain employers. We may also see any of the checks we discussed as being common at \nthe initiation of employment repeated in a similar fashion.  \n\u2022 Whether such checks occur or not often depends on the specific employer in question, and \nsome employers may not conduct them at all.  \n4.2.3 Protecting data  \n\u2022 Second only to the safety of our personnel is the safety of our data. One of our primary means \nof protecting data is the use of encryption. Although this is a reasonably sure solution, certain \nattacks may render it useless, such as those that break the encryption algorithm itself, or use \nother means to obtain the encryption keys.  \n\u2022 Another layer of security we need to ensure is the physical element. If we keep our physical \nstorage media physically safe against attackers, unfavourable environmental conditions, or \nother threats that might harm them, we place ourselves on a considerably more sound security \nfooting. \n(a) Physical Concerns for Data", "chunk_id": "545d96d3-0a9c-4616-83a2-70744c500aa4", "chroma:document": "147 \n \nimportant that we train our personnel to evacuate safely, and to respond quickly and properly \nwhen the signal to evacuate has been given. \n(e) Administrative Controls \n\u2022 We may, and likely will, also have a variety of administrative controls in place to protect \npeople, in addition to the physical measures we put in place."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 9e1cf720-3221-4aad-bbe0-5ae344064ac8
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 146, "full_page_content": "147 \n \nimportant that we train our personnel to evacuate safely, and to respond quickly and properly \nwhen the signal to evacuate has been given. \n(e) Administrative Controls \n\u2022 We may, and likely will, also have a variety of administrative controls in place to protect \npeople, in addition to the physical measures we put in place.  \n\u2022 Administrative controls are usually based on rules of some variety.  \n\u2022 More specifically, they may be policies, procedures, guidelines, regulations, laws, or similar \nbodies, and may be instituted at any level from informal company policies to federal laws.  \n\u2022 Companies put several common practices in place specifically to protect our people and our \ninterests in general. One of the most common is the background check.  \n\u2022 When an individual has made it far enough through the hiring process that it seems likely he \nor she will be hired, the hiring company will often institute a background check.  \n\u2022 A number of companies globally carry out such background checks, including AccuScreen \nand LexisNexis.  \n\u2022 Such investigations will typically involve checks for criminal history, verification of previous \nemployment, verification of education, credit checks, drug testing, and other items, depending \non the position being pursued.  \n\u2022 We may also conduct a variety of reoccurring checks on those in our employ.  \n\u2022 One of the more common and well-known examples can be seen in the drug tests conducted \nby certain employers. We may also see any of the checks we discussed as being common at \nthe initiation of employment repeated in a similar fashion.  \n\u2022 Whether such checks occur or not often depends on the specific employer in question, and \nsome employers may not conduct them at all.  \n4.2.3 Protecting data  \n\u2022 Second only to the safety of our personnel is the safety of our data. One of our primary means \nof protecting data is the use of encryption. Although this is a reasonably sure solution, certain \nattacks may render it useless, such as those that break the encryption algorithm itself, or use \nother means to obtain the encryption keys.  \n\u2022 Another layer of security we need to ensure is the physical element. If we keep our physical \nstorage media physically safe against attackers, unfavourable environmental conditions, or \nother threats that might harm them, we place ourselves on a considerably more sound security \nfooting. \n(a) Physical Concerns for Data", "chunk_id": "78f48545-cabc-48c7-9789-8722b42c82bb", "chroma:document": "\u2022 Administrative controls are usually based on rules of some variety.  \n\u2022 More specifically, they may be policies, procedures, guidelines, regulations, laws, or similar \nbodies, and may be instituted at any level from informal company policies to federal laws.  \n\u2022 Companies put several common practices in place specifically to protect our people and our"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: f579f4d8-c9f5-4e43-891c-ed42af81b149
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 146, "full_page_content": "147 \n \nimportant that we train our personnel to evacuate safely, and to respond quickly and properly \nwhen the signal to evacuate has been given. \n(e) Administrative Controls \n\u2022 We may, and likely will, also have a variety of administrative controls in place to protect \npeople, in addition to the physical measures we put in place.  \n\u2022 Administrative controls are usually based on rules of some variety.  \n\u2022 More specifically, they may be policies, procedures, guidelines, regulations, laws, or similar \nbodies, and may be instituted at any level from informal company policies to federal laws.  \n\u2022 Companies put several common practices in place specifically to protect our people and our \ninterests in general. One of the most common is the background check.  \n\u2022 When an individual has made it far enough through the hiring process that it seems likely he \nor she will be hired, the hiring company will often institute a background check.  \n\u2022 A number of companies globally carry out such background checks, including AccuScreen \nand LexisNexis.  \n\u2022 Such investigations will typically involve checks for criminal history, verification of previous \nemployment, verification of education, credit checks, drug testing, and other items, depending \non the position being pursued.  \n\u2022 We may also conduct a variety of reoccurring checks on those in our employ.  \n\u2022 One of the more common and well-known examples can be seen in the drug tests conducted \nby certain employers. We may also see any of the checks we discussed as being common at \nthe initiation of employment repeated in a similar fashion.  \n\u2022 Whether such checks occur or not often depends on the specific employer in question, and \nsome employers may not conduct them at all.  \n4.2.3 Protecting data  \n\u2022 Second only to the safety of our personnel is the safety of our data. One of our primary means \nof protecting data is the use of encryption. Although this is a reasonably sure solution, certain \nattacks may render it useless, such as those that break the encryption algorithm itself, or use \nother means to obtain the encryption keys.  \n\u2022 Another layer of security we need to ensure is the physical element. If we keep our physical \nstorage media physically safe against attackers, unfavourable environmental conditions, or \nother threats that might harm them, we place ourselves on a considerably more sound security \nfooting. \n(a) Physical Concerns for Data", "chunk_id": "0ce4a2db-fa8e-4c67-b230-ae41fc3e3e46", "chroma:document": "interests in general. One of the most common is the background check.  \n\u2022 When an individual has made it far enough through the hiring process that it seems likely he \nor she will be hired, the hiring company will often institute a background check.  \n\u2022 A number of companies globally carry out such background checks, including AccuScreen \nand LexisNexis."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 505ee485-73c7-4801-be3a-dac494f489a2
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 146, "full_page_content": "147 \n \nimportant that we train our personnel to evacuate safely, and to respond quickly and properly \nwhen the signal to evacuate has been given. \n(e) Administrative Controls \n\u2022 We may, and likely will, also have a variety of administrative controls in place to protect \npeople, in addition to the physical measures we put in place.  \n\u2022 Administrative controls are usually based on rules of some variety.  \n\u2022 More specifically, they may be policies, procedures, guidelines, regulations, laws, or similar \nbodies, and may be instituted at any level from informal company policies to federal laws.  \n\u2022 Companies put several common practices in place specifically to protect our people and our \ninterests in general. One of the most common is the background check.  \n\u2022 When an individual has made it far enough through the hiring process that it seems likely he \nor she will be hired, the hiring company will often institute a background check.  \n\u2022 A number of companies globally carry out such background checks, including AccuScreen \nand LexisNexis.  \n\u2022 Such investigations will typically involve checks for criminal history, verification of previous \nemployment, verification of education, credit checks, drug testing, and other items, depending \non the position being pursued.  \n\u2022 We may also conduct a variety of reoccurring checks on those in our employ.  \n\u2022 One of the more common and well-known examples can be seen in the drug tests conducted \nby certain employers. We may also see any of the checks we discussed as being common at \nthe initiation of employment repeated in a similar fashion.  \n\u2022 Whether such checks occur or not often depends on the specific employer in question, and \nsome employers may not conduct them at all.  \n4.2.3 Protecting data  \n\u2022 Second only to the safety of our personnel is the safety of our data. One of our primary means \nof protecting data is the use of encryption. Although this is a reasonably sure solution, certain \nattacks may render it useless, such as those that break the encryption algorithm itself, or use \nother means to obtain the encryption keys.  \n\u2022 Another layer of security we need to ensure is the physical element. If we keep our physical \nstorage media physically safe against attackers, unfavourable environmental conditions, or \nother threats that might harm them, we place ourselves on a considerably more sound security \nfooting. \n(a) Physical Concerns for Data", "chunk_id": "c22b50ea-9d6b-4d94-910d-713e649dcf02", "chroma:document": "and LexisNexis.  \n\u2022 Such investigations will typically involve checks for criminal history, verification of previous \nemployment, verification of education, credit checks, drug testing, and other items, depending \non the position being pursued.  \n\u2022 We may also conduct a variety of reoccurring checks on those in our employ."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 65475115-d6a5-4a7a-b336-1a5868e76df4
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 146, "full_page_content": "147 \n \nimportant that we train our personnel to evacuate safely, and to respond quickly and properly \nwhen the signal to evacuate has been given. \n(e) Administrative Controls \n\u2022 We may, and likely will, also have a variety of administrative controls in place to protect \npeople, in addition to the physical measures we put in place.  \n\u2022 Administrative controls are usually based on rules of some variety.  \n\u2022 More specifically, they may be policies, procedures, guidelines, regulations, laws, or similar \nbodies, and may be instituted at any level from informal company policies to federal laws.  \n\u2022 Companies put several common practices in place specifically to protect our people and our \ninterests in general. One of the most common is the background check.  \n\u2022 When an individual has made it far enough through the hiring process that it seems likely he \nor she will be hired, the hiring company will often institute a background check.  \n\u2022 A number of companies globally carry out such background checks, including AccuScreen \nand LexisNexis.  \n\u2022 Such investigations will typically involve checks for criminal history, verification of previous \nemployment, verification of education, credit checks, drug testing, and other items, depending \non the position being pursued.  \n\u2022 We may also conduct a variety of reoccurring checks on those in our employ.  \n\u2022 One of the more common and well-known examples can be seen in the drug tests conducted \nby certain employers. We may also see any of the checks we discussed as being common at \nthe initiation of employment repeated in a similar fashion.  \n\u2022 Whether such checks occur or not often depends on the specific employer in question, and \nsome employers may not conduct them at all.  \n4.2.3 Protecting data  \n\u2022 Second only to the safety of our personnel is the safety of our data. One of our primary means \nof protecting data is the use of encryption. Although this is a reasonably sure solution, certain \nattacks may render it useless, such as those that break the encryption algorithm itself, or use \nother means to obtain the encryption keys.  \n\u2022 Another layer of security we need to ensure is the physical element. If we keep our physical \nstorage media physically safe against attackers, unfavourable environmental conditions, or \nother threats that might harm them, we place ourselves on a considerably more sound security \nfooting. \n(a) Physical Concerns for Data", "chunk_id": "0aaf9af6-7f5f-4dc3-ba6d-a1bde14069f9", "chroma:document": "\u2022 One of the more common and well-known examples can be seen in the drug tests conducted \nby certain employers. We may also see any of the checks we discussed as being common at \nthe initiation of employment repeated in a similar fashion.  \n\u2022 Whether such checks occur or not often depends on the specific employer in question, and \nsome employers may not conduct them at all."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 3cbde1ac-a7aa-49b4-a979-c562a44713fc
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 146, "full_page_content": "147 \n \nimportant that we train our personnel to evacuate safely, and to respond quickly and properly \nwhen the signal to evacuate has been given. \n(e) Administrative Controls \n\u2022 We may, and likely will, also have a variety of administrative controls in place to protect \npeople, in addition to the physical measures we put in place.  \n\u2022 Administrative controls are usually based on rules of some variety.  \n\u2022 More specifically, they may be policies, procedures, guidelines, regulations, laws, or similar \nbodies, and may be instituted at any level from informal company policies to federal laws.  \n\u2022 Companies put several common practices in place specifically to protect our people and our \ninterests in general. One of the most common is the background check.  \n\u2022 When an individual has made it far enough through the hiring process that it seems likely he \nor she will be hired, the hiring company will often institute a background check.  \n\u2022 A number of companies globally carry out such background checks, including AccuScreen \nand LexisNexis.  \n\u2022 Such investigations will typically involve checks for criminal history, verification of previous \nemployment, verification of education, credit checks, drug testing, and other items, depending \non the position being pursued.  \n\u2022 We may also conduct a variety of reoccurring checks on those in our employ.  \n\u2022 One of the more common and well-known examples can be seen in the drug tests conducted \nby certain employers. We may also see any of the checks we discussed as being common at \nthe initiation of employment repeated in a similar fashion.  \n\u2022 Whether such checks occur or not often depends on the specific employer in question, and \nsome employers may not conduct them at all.  \n4.2.3 Protecting data  \n\u2022 Second only to the safety of our personnel is the safety of our data. One of our primary means \nof protecting data is the use of encryption. Although this is a reasonably sure solution, certain \nattacks may render it useless, such as those that break the encryption algorithm itself, or use \nother means to obtain the encryption keys.  \n\u2022 Another layer of security we need to ensure is the physical element. If we keep our physical \nstorage media physically safe against attackers, unfavourable environmental conditions, or \nother threats that might harm them, we place ourselves on a considerably more sound security \nfooting. \n(a) Physical Concerns for Data", "chunk_id": "fbc29b45-881e-496d-b0eb-5960e3e0ac86", "chroma:document": "4.2.3 Protecting data  \n\u2022 Second only to the safety of our personnel is the safety of our data. One of our primary means \nof protecting data is the use of encryption. Although this is a reasonably sure solution, certain \nattacks may render it useless, such as those that break the encryption algorithm itself, or use \nother means to obtain the encryption keys."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: ebf96ffc-ca77-4aba-86ae-5e0ce6f8f1a9
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 146, "full_page_content": "147 \n \nimportant that we train our personnel to evacuate safely, and to respond quickly and properly \nwhen the signal to evacuate has been given. \n(e) Administrative Controls \n\u2022 We may, and likely will, also have a variety of administrative controls in place to protect \npeople, in addition to the physical measures we put in place.  \n\u2022 Administrative controls are usually based on rules of some variety.  \n\u2022 More specifically, they may be policies, procedures, guidelines, regulations, laws, or similar \nbodies, and may be instituted at any level from informal company policies to federal laws.  \n\u2022 Companies put several common practices in place specifically to protect our people and our \ninterests in general. One of the most common is the background check.  \n\u2022 When an individual has made it far enough through the hiring process that it seems likely he \nor she will be hired, the hiring company will often institute a background check.  \n\u2022 A number of companies globally carry out such background checks, including AccuScreen \nand LexisNexis.  \n\u2022 Such investigations will typically involve checks for criminal history, verification of previous \nemployment, verification of education, credit checks, drug testing, and other items, depending \non the position being pursued.  \n\u2022 We may also conduct a variety of reoccurring checks on those in our employ.  \n\u2022 One of the more common and well-known examples can be seen in the drug tests conducted \nby certain employers. We may also see any of the checks we discussed as being common at \nthe initiation of employment repeated in a similar fashion.  \n\u2022 Whether such checks occur or not often depends on the specific employer in question, and \nsome employers may not conduct them at all.  \n4.2.3 Protecting data  \n\u2022 Second only to the safety of our personnel is the safety of our data. One of our primary means \nof protecting data is the use of encryption. Although this is a reasonably sure solution, certain \nattacks may render it useless, such as those that break the encryption algorithm itself, or use \nother means to obtain the encryption keys.  \n\u2022 Another layer of security we need to ensure is the physical element. If we keep our physical \nstorage media physically safe against attackers, unfavourable environmental conditions, or \nother threats that might harm them, we place ourselves on a considerably more sound security \nfooting. \n(a) Physical Concerns for Data", "chunk_id": "1c7d9e5c-0d02-46d7-aa70-63795efc3c1c", "chroma:document": "\u2022 Another layer of security we need to ensure is the physical element. If we keep our physical \nstorage media physically safe against attackers, unfavourable environmental conditions, or \nother threats that might harm them, we place ourselves on a considerably more sound security \nfooting. \n(a) Physical Concerns for Data"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: f0134cf6-7f36-4756-9034-c10dd7f7f1d4
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 147, "full_page_content": "148 \n \n\u2022 Depending on the type of physical media on which our data is stored, any number of adverse \nphysical conditions may be problematic or harmful to their integrity.  \n\u2022 Such media are often sensitive to temperature, humidity, magnetic fields, electricity, impact, \nand more, with each type of media having its particular strong and weak points.  \n\u2022 Magnetic media, whether we refer to hard drives, tapes, floppy disks, or otherwise, generally \ninvolves some variety of movement and magnetically sensitive material on which the data is \nrecorded.  \n\u2022 The combination of magnetic sensitivity and moving parts often makes such storage media \nfragile in one way or another. In most cases, strong magnetic fields can harm the integrity of \ndata stored on magnetic media, with media outside of metal casing, such as magnetic tapes, \nbeing even more sensitive to such disruption.  \n\u2022 Additionally, jolting such media while it is in motion, typically while it is being read from or \nwritten to, can have a variety of undesirable effects, often rendering the media unusable. \n\u2022 Flash media, referring to the general category of media that stores data on non-volatile \nmemory chips, is actually rather hardy in nature.  \n\u2022 If we can avoid impacts that might directly crush the chips on which the data is stored and we \ndo not expose them to electrical shocks, they will generally withstand conditions that many \nother types of media will not.  \n\u2022 They are not terribly sensitive to temperature ranges below what would actually destroy the \nhousing, and will often survive brief immersion in liquid, if properly dried afterward.  \n\u2022 Some flash drives are designed specifically to survive extreme conditions that would normally \ndestroy such media, for those that might consider such conditions to be a potential issue.  \n\u2022 Optical media, such as CDs and DVDs, is fairly fragile, as those with small children can attest \nto. Even small scratches on the surface of the media may render it unusable.  \n\u2022 It is also very temperature sensitive, being constructed largely of plastic and thin metal foil. \nOutside of a protected environment, such as a purpose- built media storage vault, any of a \nvariety of threats may destroy the data on such media. \n(b) Availability  \n\u2022 One of our larger concerns when we discuss protecting data is to ensure that the data is \navailable to us when we need to access it.  \n\u2022 The availability of our data often hinges on both our equipment and our facilities remaining \nin functioning condition, as we discussed earlier, and the media on which our data is stored \nbeing in working condition.", "chunk_id": "6d4c1f84-2231-4a90-b66f-a1b4b6b4a754", "chroma:document": "148 \n \n\u2022 Depending on the type of physical media on which our data is stored, any number of adverse \nphysical conditions may be problematic or harmful to their integrity.  \n\u2022 Such media are often sensitive to temperature, humidity, magnetic fields, electricity, impact, \nand more, with each type of media having its particular strong and weak points."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: c35bd3e6-639d-4d87-82af-683a2850f093
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 147, "full_page_content": "148 \n \n\u2022 Depending on the type of physical media on which our data is stored, any number of adverse \nphysical conditions may be problematic or harmful to their integrity.  \n\u2022 Such media are often sensitive to temperature, humidity, magnetic fields, electricity, impact, \nand more, with each type of media having its particular strong and weak points.  \n\u2022 Magnetic media, whether we refer to hard drives, tapes, floppy disks, or otherwise, generally \ninvolves some variety of movement and magnetically sensitive material on which the data is \nrecorded.  \n\u2022 The combination of magnetic sensitivity and moving parts often makes such storage media \nfragile in one way or another. In most cases, strong magnetic fields can harm the integrity of \ndata stored on magnetic media, with media outside of metal casing, such as magnetic tapes, \nbeing even more sensitive to such disruption.  \n\u2022 Additionally, jolting such media while it is in motion, typically while it is being read from or \nwritten to, can have a variety of undesirable effects, often rendering the media unusable. \n\u2022 Flash media, referring to the general category of media that stores data on non-volatile \nmemory chips, is actually rather hardy in nature.  \n\u2022 If we can avoid impacts that might directly crush the chips on which the data is stored and we \ndo not expose them to electrical shocks, they will generally withstand conditions that many \nother types of media will not.  \n\u2022 They are not terribly sensitive to temperature ranges below what would actually destroy the \nhousing, and will often survive brief immersion in liquid, if properly dried afterward.  \n\u2022 Some flash drives are designed specifically to survive extreme conditions that would normally \ndestroy such media, for those that might consider such conditions to be a potential issue.  \n\u2022 Optical media, such as CDs and DVDs, is fairly fragile, as those with small children can attest \nto. Even small scratches on the surface of the media may render it unusable.  \n\u2022 It is also very temperature sensitive, being constructed largely of plastic and thin metal foil. \nOutside of a protected environment, such as a purpose- built media storage vault, any of a \nvariety of threats may destroy the data on such media. \n(b) Availability  \n\u2022 One of our larger concerns when we discuss protecting data is to ensure that the data is \navailable to us when we need to access it.  \n\u2022 The availability of our data often hinges on both our equipment and our facilities remaining \nin functioning condition, as we discussed earlier, and the media on which our data is stored \nbeing in working condition.", "chunk_id": "53005ffd-8cce-414a-8021-4d4ec11500ca", "chroma:document": "\u2022 Magnetic media, whether we refer to hard drives, tapes, floppy disks, or otherwise, generally \ninvolves some variety of movement and magnetically sensitive material on which the data is \nrecorded.  \n\u2022 The combination of magnetic sensitivity and moving parts often makes such storage media"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 4ff70c31-d573-4560-a6fc-e6fd8c38cc9c
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 147, "full_page_content": "148 \n \n\u2022 Depending on the type of physical media on which our data is stored, any number of adverse \nphysical conditions may be problematic or harmful to their integrity.  \n\u2022 Such media are often sensitive to temperature, humidity, magnetic fields, electricity, impact, \nand more, with each type of media having its particular strong and weak points.  \n\u2022 Magnetic media, whether we refer to hard drives, tapes, floppy disks, or otherwise, generally \ninvolves some variety of movement and magnetically sensitive material on which the data is \nrecorded.  \n\u2022 The combination of magnetic sensitivity and moving parts often makes such storage media \nfragile in one way or another. In most cases, strong magnetic fields can harm the integrity of \ndata stored on magnetic media, with media outside of metal casing, such as magnetic tapes, \nbeing even more sensitive to such disruption.  \n\u2022 Additionally, jolting such media while it is in motion, typically while it is being read from or \nwritten to, can have a variety of undesirable effects, often rendering the media unusable. \n\u2022 Flash media, referring to the general category of media that stores data on non-volatile \nmemory chips, is actually rather hardy in nature.  \n\u2022 If we can avoid impacts that might directly crush the chips on which the data is stored and we \ndo not expose them to electrical shocks, they will generally withstand conditions that many \nother types of media will not.  \n\u2022 They are not terribly sensitive to temperature ranges below what would actually destroy the \nhousing, and will often survive brief immersion in liquid, if properly dried afterward.  \n\u2022 Some flash drives are designed specifically to survive extreme conditions that would normally \ndestroy such media, for those that might consider such conditions to be a potential issue.  \n\u2022 Optical media, such as CDs and DVDs, is fairly fragile, as those with small children can attest \nto. Even small scratches on the surface of the media may render it unusable.  \n\u2022 It is also very temperature sensitive, being constructed largely of plastic and thin metal foil. \nOutside of a protected environment, such as a purpose- built media storage vault, any of a \nvariety of threats may destroy the data on such media. \n(b) Availability  \n\u2022 One of our larger concerns when we discuss protecting data is to ensure that the data is \navailable to us when we need to access it.  \n\u2022 The availability of our data often hinges on both our equipment and our facilities remaining \nin functioning condition, as we discussed earlier, and the media on which our data is stored \nbeing in working condition.", "chunk_id": "916bd56d-5ef1-45b9-a1d8-d686e4f11b0a", "chroma:document": "fragile in one way or another. In most cases, strong magnetic fields can harm the integrity of \ndata stored on magnetic media, with media outside of metal casing, such as magnetic tapes, \nbeing even more sensitive to such disruption.  \n\u2022 Additionally, jolting such media while it is in motion, typically while it is being read from or"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: a4388779-cd3a-432c-8617-a8b9f90dae2f
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 147, "full_page_content": "148 \n \n\u2022 Depending on the type of physical media on which our data is stored, any number of adverse \nphysical conditions may be problematic or harmful to their integrity.  \n\u2022 Such media are often sensitive to temperature, humidity, magnetic fields, electricity, impact, \nand more, with each type of media having its particular strong and weak points.  \n\u2022 Magnetic media, whether we refer to hard drives, tapes, floppy disks, or otherwise, generally \ninvolves some variety of movement and magnetically sensitive material on which the data is \nrecorded.  \n\u2022 The combination of magnetic sensitivity and moving parts often makes such storage media \nfragile in one way or another. In most cases, strong magnetic fields can harm the integrity of \ndata stored on magnetic media, with media outside of metal casing, such as magnetic tapes, \nbeing even more sensitive to such disruption.  \n\u2022 Additionally, jolting such media while it is in motion, typically while it is being read from or \nwritten to, can have a variety of undesirable effects, often rendering the media unusable. \n\u2022 Flash media, referring to the general category of media that stores data on non-volatile \nmemory chips, is actually rather hardy in nature.  \n\u2022 If we can avoid impacts that might directly crush the chips on which the data is stored and we \ndo not expose them to electrical shocks, they will generally withstand conditions that many \nother types of media will not.  \n\u2022 They are not terribly sensitive to temperature ranges below what would actually destroy the \nhousing, and will often survive brief immersion in liquid, if properly dried afterward.  \n\u2022 Some flash drives are designed specifically to survive extreme conditions that would normally \ndestroy such media, for those that might consider such conditions to be a potential issue.  \n\u2022 Optical media, such as CDs and DVDs, is fairly fragile, as those with small children can attest \nto. Even small scratches on the surface of the media may render it unusable.  \n\u2022 It is also very temperature sensitive, being constructed largely of plastic and thin metal foil. \nOutside of a protected environment, such as a purpose- built media storage vault, any of a \nvariety of threats may destroy the data on such media. \n(b) Availability  \n\u2022 One of our larger concerns when we discuss protecting data is to ensure that the data is \navailable to us when we need to access it.  \n\u2022 The availability of our data often hinges on both our equipment and our facilities remaining \nin functioning condition, as we discussed earlier, and the media on which our data is stored \nbeing in working condition.", "chunk_id": "714c512d-3994-4d9c-8381-872f7877a2d9", "chroma:document": "written to, can have a variety of undesirable effects, often rendering the media unusable. \n\u2022 Flash media, referring to the general category of media that stores data on non-volatile \nmemory chips, is actually rather hardy in nature.  \n\u2022 If we can avoid impacts that might directly crush the chips on which the data is stored and we"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 92ed9769-4c7e-4fba-abd2-4f5c816d17a1
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 147, "full_page_content": "148 \n \n\u2022 Depending on the type of physical media on which our data is stored, any number of adverse \nphysical conditions may be problematic or harmful to their integrity.  \n\u2022 Such media are often sensitive to temperature, humidity, magnetic fields, electricity, impact, \nand more, with each type of media having its particular strong and weak points.  \n\u2022 Magnetic media, whether we refer to hard drives, tapes, floppy disks, or otherwise, generally \ninvolves some variety of movement and magnetically sensitive material on which the data is \nrecorded.  \n\u2022 The combination of magnetic sensitivity and moving parts often makes such storage media \nfragile in one way or another. In most cases, strong magnetic fields can harm the integrity of \ndata stored on magnetic media, with media outside of metal casing, such as magnetic tapes, \nbeing even more sensitive to such disruption.  \n\u2022 Additionally, jolting such media while it is in motion, typically while it is being read from or \nwritten to, can have a variety of undesirable effects, often rendering the media unusable. \n\u2022 Flash media, referring to the general category of media that stores data on non-volatile \nmemory chips, is actually rather hardy in nature.  \n\u2022 If we can avoid impacts that might directly crush the chips on which the data is stored and we \ndo not expose them to electrical shocks, they will generally withstand conditions that many \nother types of media will not.  \n\u2022 They are not terribly sensitive to temperature ranges below what would actually destroy the \nhousing, and will often survive brief immersion in liquid, if properly dried afterward.  \n\u2022 Some flash drives are designed specifically to survive extreme conditions that would normally \ndestroy such media, for those that might consider such conditions to be a potential issue.  \n\u2022 Optical media, such as CDs and DVDs, is fairly fragile, as those with small children can attest \nto. Even small scratches on the surface of the media may render it unusable.  \n\u2022 It is also very temperature sensitive, being constructed largely of plastic and thin metal foil. \nOutside of a protected environment, such as a purpose- built media storage vault, any of a \nvariety of threats may destroy the data on such media. \n(b) Availability  \n\u2022 One of our larger concerns when we discuss protecting data is to ensure that the data is \navailable to us when we need to access it.  \n\u2022 The availability of our data often hinges on both our equipment and our facilities remaining \nin functioning condition, as we discussed earlier, and the media on which our data is stored \nbeing in working condition.", "chunk_id": "f561042b-7185-45dd-a126-76829efa9242", "chroma:document": "do not expose them to electrical shocks, they will generally withstand conditions that many \nother types of media will not.  \n\u2022 They are not terribly sensitive to temperature ranges below what would actually destroy the \nhousing, and will often survive brief immersion in liquid, if properly dried afterward."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 105cf537-1dcd-4129-a55f-4700ee78d105
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 147, "full_page_content": "148 \n \n\u2022 Depending on the type of physical media on which our data is stored, any number of adverse \nphysical conditions may be problematic or harmful to their integrity.  \n\u2022 Such media are often sensitive to temperature, humidity, magnetic fields, electricity, impact, \nand more, with each type of media having its particular strong and weak points.  \n\u2022 Magnetic media, whether we refer to hard drives, tapes, floppy disks, or otherwise, generally \ninvolves some variety of movement and magnetically sensitive material on which the data is \nrecorded.  \n\u2022 The combination of magnetic sensitivity and moving parts often makes such storage media \nfragile in one way or another. In most cases, strong magnetic fields can harm the integrity of \ndata stored on magnetic media, with media outside of metal casing, such as magnetic tapes, \nbeing even more sensitive to such disruption.  \n\u2022 Additionally, jolting such media while it is in motion, typically while it is being read from or \nwritten to, can have a variety of undesirable effects, often rendering the media unusable. \n\u2022 Flash media, referring to the general category of media that stores data on non-volatile \nmemory chips, is actually rather hardy in nature.  \n\u2022 If we can avoid impacts that might directly crush the chips on which the data is stored and we \ndo not expose them to electrical shocks, they will generally withstand conditions that many \nother types of media will not.  \n\u2022 They are not terribly sensitive to temperature ranges below what would actually destroy the \nhousing, and will often survive brief immersion in liquid, if properly dried afterward.  \n\u2022 Some flash drives are designed specifically to survive extreme conditions that would normally \ndestroy such media, for those that might consider such conditions to be a potential issue.  \n\u2022 Optical media, such as CDs and DVDs, is fairly fragile, as those with small children can attest \nto. Even small scratches on the surface of the media may render it unusable.  \n\u2022 It is also very temperature sensitive, being constructed largely of plastic and thin metal foil. \nOutside of a protected environment, such as a purpose- built media storage vault, any of a \nvariety of threats may destroy the data on such media. \n(b) Availability  \n\u2022 One of our larger concerns when we discuss protecting data is to ensure that the data is \navailable to us when we need to access it.  \n\u2022 The availability of our data often hinges on both our equipment and our facilities remaining \nin functioning condition, as we discussed earlier, and the media on which our data is stored \nbeing in working condition.", "chunk_id": "76cbe716-c143-4b9c-80fe-99890fbb6f46", "chroma:document": "\u2022 Some flash drives are designed specifically to survive extreme conditions that would normally \ndestroy such media, for those that might consider such conditions to be a potential issue.  \n\u2022 Optical media, such as CDs and DVDs, is fairly fragile, as those with small children can attest \nto. Even small scratches on the surface of the media may render it unusable."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: b965af34-b5f5-4967-9bb5-8954fa73980c
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 147, "full_page_content": "148 \n \n\u2022 Depending on the type of physical media on which our data is stored, any number of adverse \nphysical conditions may be problematic or harmful to their integrity.  \n\u2022 Such media are often sensitive to temperature, humidity, magnetic fields, electricity, impact, \nand more, with each type of media having its particular strong and weak points.  \n\u2022 Magnetic media, whether we refer to hard drives, tapes, floppy disks, or otherwise, generally \ninvolves some variety of movement and magnetically sensitive material on which the data is \nrecorded.  \n\u2022 The combination of magnetic sensitivity and moving parts often makes such storage media \nfragile in one way or another. In most cases, strong magnetic fields can harm the integrity of \ndata stored on magnetic media, with media outside of metal casing, such as magnetic tapes, \nbeing even more sensitive to such disruption.  \n\u2022 Additionally, jolting such media while it is in motion, typically while it is being read from or \nwritten to, can have a variety of undesirable effects, often rendering the media unusable. \n\u2022 Flash media, referring to the general category of media that stores data on non-volatile \nmemory chips, is actually rather hardy in nature.  \n\u2022 If we can avoid impacts that might directly crush the chips on which the data is stored and we \ndo not expose them to electrical shocks, they will generally withstand conditions that many \nother types of media will not.  \n\u2022 They are not terribly sensitive to temperature ranges below what would actually destroy the \nhousing, and will often survive brief immersion in liquid, if properly dried afterward.  \n\u2022 Some flash drives are designed specifically to survive extreme conditions that would normally \ndestroy such media, for those that might consider such conditions to be a potential issue.  \n\u2022 Optical media, such as CDs and DVDs, is fairly fragile, as those with small children can attest \nto. Even small scratches on the surface of the media may render it unusable.  \n\u2022 It is also very temperature sensitive, being constructed largely of plastic and thin metal foil. \nOutside of a protected environment, such as a purpose- built media storage vault, any of a \nvariety of threats may destroy the data on such media. \n(b) Availability  \n\u2022 One of our larger concerns when we discuss protecting data is to ensure that the data is \navailable to us when we need to access it.  \n\u2022 The availability of our data often hinges on both our equipment and our facilities remaining \nin functioning condition, as we discussed earlier, and the media on which our data is stored \nbeing in working condition.", "chunk_id": "ed5e4379-698b-41d1-8694-cd0e97593399", "chroma:document": "\u2022 It is also very temperature sensitive, being constructed largely of plastic and thin metal foil. \nOutside of a protected environment, such as a purpose- built media storage vault, any of a \nvariety of threats may destroy the data on such media. \n(b) Availability  \n\u2022 One of our larger concerns when we discuss protecting data is to ensure that the data is"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 6124ffee-5566-467b-afe5-b5330f2ad577
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 147, "full_page_content": "148 \n \n\u2022 Depending on the type of physical media on which our data is stored, any number of adverse \nphysical conditions may be problematic or harmful to their integrity.  \n\u2022 Such media are often sensitive to temperature, humidity, magnetic fields, electricity, impact, \nand more, with each type of media having its particular strong and weak points.  \n\u2022 Magnetic media, whether we refer to hard drives, tapes, floppy disks, or otherwise, generally \ninvolves some variety of movement and magnetically sensitive material on which the data is \nrecorded.  \n\u2022 The combination of magnetic sensitivity and moving parts often makes such storage media \nfragile in one way or another. In most cases, strong magnetic fields can harm the integrity of \ndata stored on magnetic media, with media outside of metal casing, such as magnetic tapes, \nbeing even more sensitive to such disruption.  \n\u2022 Additionally, jolting such media while it is in motion, typically while it is being read from or \nwritten to, can have a variety of undesirable effects, often rendering the media unusable. \n\u2022 Flash media, referring to the general category of media that stores data on non-volatile \nmemory chips, is actually rather hardy in nature.  \n\u2022 If we can avoid impacts that might directly crush the chips on which the data is stored and we \ndo not expose them to electrical shocks, they will generally withstand conditions that many \nother types of media will not.  \n\u2022 They are not terribly sensitive to temperature ranges below what would actually destroy the \nhousing, and will often survive brief immersion in liquid, if properly dried afterward.  \n\u2022 Some flash drives are designed specifically to survive extreme conditions that would normally \ndestroy such media, for those that might consider such conditions to be a potential issue.  \n\u2022 Optical media, such as CDs and DVDs, is fairly fragile, as those with small children can attest \nto. Even small scratches on the surface of the media may render it unusable.  \n\u2022 It is also very temperature sensitive, being constructed largely of plastic and thin metal foil. \nOutside of a protected environment, such as a purpose- built media storage vault, any of a \nvariety of threats may destroy the data on such media. \n(b) Availability  \n\u2022 One of our larger concerns when we discuss protecting data is to ensure that the data is \navailable to us when we need to access it.  \n\u2022 The availability of our data often hinges on both our equipment and our facilities remaining \nin functioning condition, as we discussed earlier, and the media on which our data is stored \nbeing in working condition.", "chunk_id": "b43bb2bf-e5ff-4a3a-9d9d-78c4ab8eaf18", "chroma:document": "available to us when we need to access it.  \n\u2022 The availability of our data often hinges on both our equipment and our facilities remaining \nin functioning condition, as we discussed earlier, and the media on which our data is stored \nbeing in working condition."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 180acdd3-959d-4ac1-98f9-d7326721713a
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 148, "full_page_content": "149 \n \n\u2022 Any of the physical concerns we discussed earlier can render our data inaccessible, in the \nsense of being able to read it from the media on which it is stored Although we are specifically \ndiscussing access to data here, and we talked about some of the potential hardware issues in \naccessing certain types of media earlier there is also a fairly substantial equipment and \ninfrastructure component to consider when discussing availability.  \n\u2022 Not only can we experience issues in reading the data from the media, but we may also have \nproblems in getting to where the data is stored.  \n\u2022 If we are experiencing an outage, whether it is related to network, power, computer systems, \nor other components, at any point between our location and a remote data location, we may \nnot be able to access our data remotely.  \n\u2022 Many businesses operate globally today, and it is possible that the loss of ability to access \ndata remotely, even temporarily, will be a rather serious issue.   \n(c) Residual Data  \n\u2022 When we look at the idea of keeping data safe, we not only need to have the data available \nwhen we need access to it, but we also must be able to render the data inaccessible when it is \nno longer required.  \n\u2022 In some cases, this need is relatively obvious; for instance, we might not overlook the need \nto shred a stack of paper containing sensitive data before we throw it away. But the data stored \non electronic media may not present itself so clearly to everyone that might be handling it or \ndisposing of it. \n\u2022 In many cases, we can find stored data in several computing-related devices, such as \ncomputers, disk arrays, portable media devices, flash drives, backup tapes, CD or DVD \nmedia, and similar items.  \n\u2022 We would hope that the relatively computer savvy people would realize the media or device \nmight contain some sensitive data, and that they should erase the data before they dispose of \nit.  \n\u2022 Unfortunately, this is not always the case. In the early 2000s, a study was conducted on more \nthan 150 used hard drives purchased from a variety of different sources, with a large number \nof them being purchased from eBay.  \n\u2022 When the contents of the disks were analyzed, it was discovered that many of them still \ncontained data, to include medical data, pornography, e-mail messages, and several disks that \nappeared to have been used for financial data containing more than 6,500 credit card numbers.  \nIn many cases, no attempt had been made to erase the data from the disks", "chunk_id": "01d26e7c-9b70-4c78-9565-0255b4c092d9", "chroma:document": "149 \n \n\u2022 Any of the physical concerns we discussed earlier can render our data inaccessible, in the \nsense of being able to read it from the media on which it is stored Although we are specifically \ndiscussing access to data here, and we talked about some of the potential hardware issues in \naccessing certain types of media earlier there is also a fairly substantial equipment and"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: f6753474-0df1-40fd-89e4-679dc87f549f
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 148, "full_page_content": "149 \n \n\u2022 Any of the physical concerns we discussed earlier can render our data inaccessible, in the \nsense of being able to read it from the media on which it is stored Although we are specifically \ndiscussing access to data here, and we talked about some of the potential hardware issues in \naccessing certain types of media earlier there is also a fairly substantial equipment and \ninfrastructure component to consider when discussing availability.  \n\u2022 Not only can we experience issues in reading the data from the media, but we may also have \nproblems in getting to where the data is stored.  \n\u2022 If we are experiencing an outage, whether it is related to network, power, computer systems, \nor other components, at any point between our location and a remote data location, we may \nnot be able to access our data remotely.  \n\u2022 Many businesses operate globally today, and it is possible that the loss of ability to access \ndata remotely, even temporarily, will be a rather serious issue.   \n(c) Residual Data  \n\u2022 When we look at the idea of keeping data safe, we not only need to have the data available \nwhen we need access to it, but we also must be able to render the data inaccessible when it is \nno longer required.  \n\u2022 In some cases, this need is relatively obvious; for instance, we might not overlook the need \nto shred a stack of paper containing sensitive data before we throw it away. But the data stored \non electronic media may not present itself so clearly to everyone that might be handling it or \ndisposing of it. \n\u2022 In many cases, we can find stored data in several computing-related devices, such as \ncomputers, disk arrays, portable media devices, flash drives, backup tapes, CD or DVD \nmedia, and similar items.  \n\u2022 We would hope that the relatively computer savvy people would realize the media or device \nmight contain some sensitive data, and that they should erase the data before they dispose of \nit.  \n\u2022 Unfortunately, this is not always the case. In the early 2000s, a study was conducted on more \nthan 150 used hard drives purchased from a variety of different sources, with a large number \nof them being purchased from eBay.  \n\u2022 When the contents of the disks were analyzed, it was discovered that many of them still \ncontained data, to include medical data, pornography, e-mail messages, and several disks that \nappeared to have been used for financial data containing more than 6,500 credit card numbers.  \nIn many cases, no attempt had been made to erase the data from the disks", "chunk_id": "a039de86-cba4-42b9-a46e-3506906deff2", "chroma:document": "infrastructure component to consider when discussing availability.  \n\u2022 Not only can we experience issues in reading the data from the media, but we may also have \nproblems in getting to where the data is stored.  \n\u2022 If we are experiencing an outage, whether it is related to network, power, computer systems,"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 94c6a489-1b2a-4513-aaba-da29c3225db4
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 148, "full_page_content": "149 \n \n\u2022 Any of the physical concerns we discussed earlier can render our data inaccessible, in the \nsense of being able to read it from the media on which it is stored Although we are specifically \ndiscussing access to data here, and we talked about some of the potential hardware issues in \naccessing certain types of media earlier there is also a fairly substantial equipment and \ninfrastructure component to consider when discussing availability.  \n\u2022 Not only can we experience issues in reading the data from the media, but we may also have \nproblems in getting to where the data is stored.  \n\u2022 If we are experiencing an outage, whether it is related to network, power, computer systems, \nor other components, at any point between our location and a remote data location, we may \nnot be able to access our data remotely.  \n\u2022 Many businesses operate globally today, and it is possible that the loss of ability to access \ndata remotely, even temporarily, will be a rather serious issue.   \n(c) Residual Data  \n\u2022 When we look at the idea of keeping data safe, we not only need to have the data available \nwhen we need access to it, but we also must be able to render the data inaccessible when it is \nno longer required.  \n\u2022 In some cases, this need is relatively obvious; for instance, we might not overlook the need \nto shred a stack of paper containing sensitive data before we throw it away. But the data stored \non electronic media may not present itself so clearly to everyone that might be handling it or \ndisposing of it. \n\u2022 In many cases, we can find stored data in several computing-related devices, such as \ncomputers, disk arrays, portable media devices, flash drives, backup tapes, CD or DVD \nmedia, and similar items.  \n\u2022 We would hope that the relatively computer savvy people would realize the media or device \nmight contain some sensitive data, and that they should erase the data before they dispose of \nit.  \n\u2022 Unfortunately, this is not always the case. In the early 2000s, a study was conducted on more \nthan 150 used hard drives purchased from a variety of different sources, with a large number \nof them being purchased from eBay.  \n\u2022 When the contents of the disks were analyzed, it was discovered that many of them still \ncontained data, to include medical data, pornography, e-mail messages, and several disks that \nappeared to have been used for financial data containing more than 6,500 credit card numbers.  \nIn many cases, no attempt had been made to erase the data from the disks", "chunk_id": "6548c887-f7fe-4526-8866-f22bd93df6ca", "chroma:document": "or other components, at any point between our location and a remote data location, we may \nnot be able to access our data remotely.  \n\u2022 Many businesses operate globally today, and it is possible that the loss of ability to access \ndata remotely, even temporarily, will be a rather serious issue.   \n(c) Residual Data"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 67cfb931-43be-41c2-8994-4ed317edbdb0
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 148, "full_page_content": "149 \n \n\u2022 Any of the physical concerns we discussed earlier can render our data inaccessible, in the \nsense of being able to read it from the media on which it is stored Although we are specifically \ndiscussing access to data here, and we talked about some of the potential hardware issues in \naccessing certain types of media earlier there is also a fairly substantial equipment and \ninfrastructure component to consider when discussing availability.  \n\u2022 Not only can we experience issues in reading the data from the media, but we may also have \nproblems in getting to where the data is stored.  \n\u2022 If we are experiencing an outage, whether it is related to network, power, computer systems, \nor other components, at any point between our location and a remote data location, we may \nnot be able to access our data remotely.  \n\u2022 Many businesses operate globally today, and it is possible that the loss of ability to access \ndata remotely, even temporarily, will be a rather serious issue.   \n(c) Residual Data  \n\u2022 When we look at the idea of keeping data safe, we not only need to have the data available \nwhen we need access to it, but we also must be able to render the data inaccessible when it is \nno longer required.  \n\u2022 In some cases, this need is relatively obvious; for instance, we might not overlook the need \nto shred a stack of paper containing sensitive data before we throw it away. But the data stored \non electronic media may not present itself so clearly to everyone that might be handling it or \ndisposing of it. \n\u2022 In many cases, we can find stored data in several computing-related devices, such as \ncomputers, disk arrays, portable media devices, flash drives, backup tapes, CD or DVD \nmedia, and similar items.  \n\u2022 We would hope that the relatively computer savvy people would realize the media or device \nmight contain some sensitive data, and that they should erase the data before they dispose of \nit.  \n\u2022 Unfortunately, this is not always the case. In the early 2000s, a study was conducted on more \nthan 150 used hard drives purchased from a variety of different sources, with a large number \nof them being purchased from eBay.  \n\u2022 When the contents of the disks were analyzed, it was discovered that many of them still \ncontained data, to include medical data, pornography, e-mail messages, and several disks that \nappeared to have been used for financial data containing more than 6,500 credit card numbers.  \nIn many cases, no attempt had been made to erase the data from the disks", "chunk_id": "5713d503-d042-48c6-8bfc-358c3edaf694", "chroma:document": "(c) Residual Data  \n\u2022 When we look at the idea of keeping data safe, we not only need to have the data available \nwhen we need access to it, but we also must be able to render the data inaccessible when it is \nno longer required.  \n\u2022 In some cases, this need is relatively obvious; for instance, we might not overlook the need"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 442d87a5-cfef-47a2-a4b7-e21adb218030
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 148, "full_page_content": "149 \n \n\u2022 Any of the physical concerns we discussed earlier can render our data inaccessible, in the \nsense of being able to read it from the media on which it is stored Although we are specifically \ndiscussing access to data here, and we talked about some of the potential hardware issues in \naccessing certain types of media earlier there is also a fairly substantial equipment and \ninfrastructure component to consider when discussing availability.  \n\u2022 Not only can we experience issues in reading the data from the media, but we may also have \nproblems in getting to where the data is stored.  \n\u2022 If we are experiencing an outage, whether it is related to network, power, computer systems, \nor other components, at any point between our location and a remote data location, we may \nnot be able to access our data remotely.  \n\u2022 Many businesses operate globally today, and it is possible that the loss of ability to access \ndata remotely, even temporarily, will be a rather serious issue.   \n(c) Residual Data  \n\u2022 When we look at the idea of keeping data safe, we not only need to have the data available \nwhen we need access to it, but we also must be able to render the data inaccessible when it is \nno longer required.  \n\u2022 In some cases, this need is relatively obvious; for instance, we might not overlook the need \nto shred a stack of paper containing sensitive data before we throw it away. But the data stored \non electronic media may not present itself so clearly to everyone that might be handling it or \ndisposing of it. \n\u2022 In many cases, we can find stored data in several computing-related devices, such as \ncomputers, disk arrays, portable media devices, flash drives, backup tapes, CD or DVD \nmedia, and similar items.  \n\u2022 We would hope that the relatively computer savvy people would realize the media or device \nmight contain some sensitive data, and that they should erase the data before they dispose of \nit.  \n\u2022 Unfortunately, this is not always the case. In the early 2000s, a study was conducted on more \nthan 150 used hard drives purchased from a variety of different sources, with a large number \nof them being purchased from eBay.  \n\u2022 When the contents of the disks were analyzed, it was discovered that many of them still \ncontained data, to include medical data, pornography, e-mail messages, and several disks that \nappeared to have been used for financial data containing more than 6,500 credit card numbers.  \nIn many cases, no attempt had been made to erase the data from the disks", "chunk_id": "4cfe8473-198f-4755-b061-ff2a6de6fb76", "chroma:document": "to shred a stack of paper containing sensitive data before we throw it away. But the data stored \non electronic media may not present itself so clearly to everyone that might be handling it or \ndisposing of it. \n\u2022 In many cases, we can find stored data in several computing-related devices, such as"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 08b491da-1da7-49b9-8d30-016324d2d759
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 148, "full_page_content": "149 \n \n\u2022 Any of the physical concerns we discussed earlier can render our data inaccessible, in the \nsense of being able to read it from the media on which it is stored Although we are specifically \ndiscussing access to data here, and we talked about some of the potential hardware issues in \naccessing certain types of media earlier there is also a fairly substantial equipment and \ninfrastructure component to consider when discussing availability.  \n\u2022 Not only can we experience issues in reading the data from the media, but we may also have \nproblems in getting to where the data is stored.  \n\u2022 If we are experiencing an outage, whether it is related to network, power, computer systems, \nor other components, at any point between our location and a remote data location, we may \nnot be able to access our data remotely.  \n\u2022 Many businesses operate globally today, and it is possible that the loss of ability to access \ndata remotely, even temporarily, will be a rather serious issue.   \n(c) Residual Data  \n\u2022 When we look at the idea of keeping data safe, we not only need to have the data available \nwhen we need access to it, but we also must be able to render the data inaccessible when it is \nno longer required.  \n\u2022 In some cases, this need is relatively obvious; for instance, we might not overlook the need \nto shred a stack of paper containing sensitive data before we throw it away. But the data stored \non electronic media may not present itself so clearly to everyone that might be handling it or \ndisposing of it. \n\u2022 In many cases, we can find stored data in several computing-related devices, such as \ncomputers, disk arrays, portable media devices, flash drives, backup tapes, CD or DVD \nmedia, and similar items.  \n\u2022 We would hope that the relatively computer savvy people would realize the media or device \nmight contain some sensitive data, and that they should erase the data before they dispose of \nit.  \n\u2022 Unfortunately, this is not always the case. In the early 2000s, a study was conducted on more \nthan 150 used hard drives purchased from a variety of different sources, with a large number \nof them being purchased from eBay.  \n\u2022 When the contents of the disks were analyzed, it was discovered that many of them still \ncontained data, to include medical data, pornography, e-mail messages, and several disks that \nappeared to have been used for financial data containing more than 6,500 credit card numbers.  \nIn many cases, no attempt had been made to erase the data from the disks", "chunk_id": "da8569d9-36f1-43d4-839b-f21d5b77cb5e", "chroma:document": "computers, disk arrays, portable media devices, flash drives, backup tapes, CD or DVD \nmedia, and similar items.  \n\u2022 We would hope that the relatively computer savvy people would realize the media or device \nmight contain some sensitive data, and that they should erase the data before they dispose of \nit."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 35e6af78-dc15-4f7c-a650-833dbc66c8e7
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 148, "full_page_content": "149 \n \n\u2022 Any of the physical concerns we discussed earlier can render our data inaccessible, in the \nsense of being able to read it from the media on which it is stored Although we are specifically \ndiscussing access to data here, and we talked about some of the potential hardware issues in \naccessing certain types of media earlier there is also a fairly substantial equipment and \ninfrastructure component to consider when discussing availability.  \n\u2022 Not only can we experience issues in reading the data from the media, but we may also have \nproblems in getting to where the data is stored.  \n\u2022 If we are experiencing an outage, whether it is related to network, power, computer systems, \nor other components, at any point between our location and a remote data location, we may \nnot be able to access our data remotely.  \n\u2022 Many businesses operate globally today, and it is possible that the loss of ability to access \ndata remotely, even temporarily, will be a rather serious issue.   \n(c) Residual Data  \n\u2022 When we look at the idea of keeping data safe, we not only need to have the data available \nwhen we need access to it, but we also must be able to render the data inaccessible when it is \nno longer required.  \n\u2022 In some cases, this need is relatively obvious; for instance, we might not overlook the need \nto shred a stack of paper containing sensitive data before we throw it away. But the data stored \non electronic media may not present itself so clearly to everyone that might be handling it or \ndisposing of it. \n\u2022 In many cases, we can find stored data in several computing-related devices, such as \ncomputers, disk arrays, portable media devices, flash drives, backup tapes, CD or DVD \nmedia, and similar items.  \n\u2022 We would hope that the relatively computer savvy people would realize the media or device \nmight contain some sensitive data, and that they should erase the data before they dispose of \nit.  \n\u2022 Unfortunately, this is not always the case. In the early 2000s, a study was conducted on more \nthan 150 used hard drives purchased from a variety of different sources, with a large number \nof them being purchased from eBay.  \n\u2022 When the contents of the disks were analyzed, it was discovered that many of them still \ncontained data, to include medical data, pornography, e-mail messages, and several disks that \nappeared to have been used for financial data containing more than 6,500 credit card numbers.  \nIn many cases, no attempt had been made to erase the data from the disks", "chunk_id": "28c7cf94-911b-4d9a-b0d1-ff56de032e4f", "chroma:document": "it.  \n\u2022 Unfortunately, this is not always the case. In the early 2000s, a study was conducted on more \nthan 150 used hard drives purchased from a variety of different sources, with a large number \nof them being purchased from eBay.  \n\u2022 When the contents of the disks were analyzed, it was discovered that many of them still"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 028e3db3-4601-458c-a2f2-9b3e5f9fb7c3
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 148, "full_page_content": "149 \n \n\u2022 Any of the physical concerns we discussed earlier can render our data inaccessible, in the \nsense of being able to read it from the media on which it is stored Although we are specifically \ndiscussing access to data here, and we talked about some of the potential hardware issues in \naccessing certain types of media earlier there is also a fairly substantial equipment and \ninfrastructure component to consider when discussing availability.  \n\u2022 Not only can we experience issues in reading the data from the media, but we may also have \nproblems in getting to where the data is stored.  \n\u2022 If we are experiencing an outage, whether it is related to network, power, computer systems, \nor other components, at any point between our location and a remote data location, we may \nnot be able to access our data remotely.  \n\u2022 Many businesses operate globally today, and it is possible that the loss of ability to access \ndata remotely, even temporarily, will be a rather serious issue.   \n(c) Residual Data  \n\u2022 When we look at the idea of keeping data safe, we not only need to have the data available \nwhen we need access to it, but we also must be able to render the data inaccessible when it is \nno longer required.  \n\u2022 In some cases, this need is relatively obvious; for instance, we might not overlook the need \nto shred a stack of paper containing sensitive data before we throw it away. But the data stored \non electronic media may not present itself so clearly to everyone that might be handling it or \ndisposing of it. \n\u2022 In many cases, we can find stored data in several computing-related devices, such as \ncomputers, disk arrays, portable media devices, flash drives, backup tapes, CD or DVD \nmedia, and similar items.  \n\u2022 We would hope that the relatively computer savvy people would realize the media or device \nmight contain some sensitive data, and that they should erase the data before they dispose of \nit.  \n\u2022 Unfortunately, this is not always the case. In the early 2000s, a study was conducted on more \nthan 150 used hard drives purchased from a variety of different sources, with a large number \nof them being purchased from eBay.  \n\u2022 When the contents of the disks were analyzed, it was discovered that many of them still \ncontained data, to include medical data, pornography, e-mail messages, and several disks that \nappeared to have been used for financial data containing more than 6,500 credit card numbers.  \nIn many cases, no attempt had been made to erase the data from the disks", "chunk_id": "7121e086-dceb-4ed4-910f-155129bf7347", "chroma:document": "contained data, to include medical data, pornography, e-mail messages, and several disks that \nappeared to have been used for financial data containing more than 6,500 credit card numbers.  \nIn many cases, no attempt had been made to erase the data from the disks"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 51eed49a-66bd-4c78-8f2c-88cabb710d74
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 149, "full_page_content": "150 \n \n(d) Backups  \n\u2022 In order to ensure that we can maintain the availability of our data, we will likely want to \nmaintain backups.  \n\u2022 Not only do we need to back up the data itself, but we also need to maintain backups of the \nequipment and infrastructure that are used to provide access to the data. We can perform data \nbackups in a number of ways.  \n\u2022 We can utilize redundant arrays of inexpensive disks (RAID) in a variety of configurations to \nensure that we do not lose data from hardware failures in individual disks, we can replicate \ndata from one machine to another over a network, or we can make copies of data onto backup \nstorage media, such as DVDs or magnetic tapes.  \n4.2.4 Protecting equipment  \n\u2022 Last on the list of our concerns for physical security, although still very important and \nsignificant, is protecting our equipment, and, to a certain extent, the facilities that house it.  \n\u2022 This category falls last on the list because it represents the easiest and cheapest segment of \nour assets to replace.  \n\u2022 Even in the case of a major disaster that completely destroys our facility and all the computing \nequipment inside it, as long as we still have the people needed to run our operation and are \nable to restore or access our critical data, we can be back in working order very shortly.  \n\u2022 Replacing floor space or relocating to another area nearby can generally be accomplished \nwith relative ease, and computing equipment is both cheap and plentiful.  \n\u2022 Although it may take us some time to be back to the same state we were in before the incident, \ngetting to a bare minimum working state technology-wise is often a simple, if arduous, task. \n \n(a) Physical Concerns for Equipment \n\u2022 The physical threats that might harm our equipment, although fewer than those we might find \nharmful to people, are still numerous.  \n\u2022 Extreme temperatures can be very harmful to equipment. We typically think of heat as being \nthe most harmful to computing equipment, and this is largely correct.  \n\u2022 In environments that contain large numbers of computers and associated equipment, such as \nin a data centre, we rely on environmental conditioning equipment to keep the temperature \ndown to a reasonable level, typically in the high-60s to mid-70s on the Fahrenheit scale, \nalthough there is some debate over the subject.", "chunk_id": "e6195af8-f00d-4626-99c4-11ce457a6db9", "chroma:document": "150 \n \n(d) Backups  \n\u2022 In order to ensure that we can maintain the availability of our data, we will likely want to \nmaintain backups.  \n\u2022 Not only do we need to back up the data itself, but we also need to maintain backups of the \nequipment and infrastructure that are used to provide access to the data. We can perform data \nbackups in a number of ways."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 6bfbcb2e-ceac-4f15-ac82-94c9ddaf44fa
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 149, "full_page_content": "150 \n \n(d) Backups  \n\u2022 In order to ensure that we can maintain the availability of our data, we will likely want to \nmaintain backups.  \n\u2022 Not only do we need to back up the data itself, but we also need to maintain backups of the \nequipment and infrastructure that are used to provide access to the data. We can perform data \nbackups in a number of ways.  \n\u2022 We can utilize redundant arrays of inexpensive disks (RAID) in a variety of configurations to \nensure that we do not lose data from hardware failures in individual disks, we can replicate \ndata from one machine to another over a network, or we can make copies of data onto backup \nstorage media, such as DVDs or magnetic tapes.  \n4.2.4 Protecting equipment  \n\u2022 Last on the list of our concerns for physical security, although still very important and \nsignificant, is protecting our equipment, and, to a certain extent, the facilities that house it.  \n\u2022 This category falls last on the list because it represents the easiest and cheapest segment of \nour assets to replace.  \n\u2022 Even in the case of a major disaster that completely destroys our facility and all the computing \nequipment inside it, as long as we still have the people needed to run our operation and are \nable to restore or access our critical data, we can be back in working order very shortly.  \n\u2022 Replacing floor space or relocating to another area nearby can generally be accomplished \nwith relative ease, and computing equipment is both cheap and plentiful.  \n\u2022 Although it may take us some time to be back to the same state we were in before the incident, \ngetting to a bare minimum working state technology-wise is often a simple, if arduous, task. \n \n(a) Physical Concerns for Equipment \n\u2022 The physical threats that might harm our equipment, although fewer than those we might find \nharmful to people, are still numerous.  \n\u2022 Extreme temperatures can be very harmful to equipment. We typically think of heat as being \nthe most harmful to computing equipment, and this is largely correct.  \n\u2022 In environments that contain large numbers of computers and associated equipment, such as \nin a data centre, we rely on environmental conditioning equipment to keep the temperature \ndown to a reasonable level, typically in the high-60s to mid-70s on the Fahrenheit scale, \nalthough there is some debate over the subject.", "chunk_id": "6a73bab4-d201-41a8-b3c7-1410cf529a1c", "chroma:document": "\u2022 We can utilize redundant arrays of inexpensive disks (RAID) in a variety of configurations to \nensure that we do not lose data from hardware failures in individual disks, we can replicate \ndata from one machine to another over a network, or we can make copies of data onto backup \nstorage media, such as DVDs or magnetic tapes.  \n4.2.4 Protecting equipment"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: c43369b9-3615-46dd-acd1-01329c9c0ed7
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 149, "full_page_content": "150 \n \n(d) Backups  \n\u2022 In order to ensure that we can maintain the availability of our data, we will likely want to \nmaintain backups.  \n\u2022 Not only do we need to back up the data itself, but we also need to maintain backups of the \nequipment and infrastructure that are used to provide access to the data. We can perform data \nbackups in a number of ways.  \n\u2022 We can utilize redundant arrays of inexpensive disks (RAID) in a variety of configurations to \nensure that we do not lose data from hardware failures in individual disks, we can replicate \ndata from one machine to another over a network, or we can make copies of data onto backup \nstorage media, such as DVDs or magnetic tapes.  \n4.2.4 Protecting equipment  \n\u2022 Last on the list of our concerns for physical security, although still very important and \nsignificant, is protecting our equipment, and, to a certain extent, the facilities that house it.  \n\u2022 This category falls last on the list because it represents the easiest and cheapest segment of \nour assets to replace.  \n\u2022 Even in the case of a major disaster that completely destroys our facility and all the computing \nequipment inside it, as long as we still have the people needed to run our operation and are \nable to restore or access our critical data, we can be back in working order very shortly.  \n\u2022 Replacing floor space or relocating to another area nearby can generally be accomplished \nwith relative ease, and computing equipment is both cheap and plentiful.  \n\u2022 Although it may take us some time to be back to the same state we were in before the incident, \ngetting to a bare minimum working state technology-wise is often a simple, if arduous, task. \n \n(a) Physical Concerns for Equipment \n\u2022 The physical threats that might harm our equipment, although fewer than those we might find \nharmful to people, are still numerous.  \n\u2022 Extreme temperatures can be very harmful to equipment. We typically think of heat as being \nthe most harmful to computing equipment, and this is largely correct.  \n\u2022 In environments that contain large numbers of computers and associated equipment, such as \nin a data centre, we rely on environmental conditioning equipment to keep the temperature \ndown to a reasonable level, typically in the high-60s to mid-70s on the Fahrenheit scale, \nalthough there is some debate over the subject.", "chunk_id": "65de9a22-d549-4007-893d-1594d510254d", "chroma:document": "\u2022 Last on the list of our concerns for physical security, although still very important and \nsignificant, is protecting our equipment, and, to a certain extent, the facilities that house it.  \n\u2022 This category falls last on the list because it represents the easiest and cheapest segment of \nour assets to replace."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: e08c7bf2-d44a-4fd4-99cc-451145b5924b
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 149, "full_page_content": "150 \n \n(d) Backups  \n\u2022 In order to ensure that we can maintain the availability of our data, we will likely want to \nmaintain backups.  \n\u2022 Not only do we need to back up the data itself, but we also need to maintain backups of the \nequipment and infrastructure that are used to provide access to the data. We can perform data \nbackups in a number of ways.  \n\u2022 We can utilize redundant arrays of inexpensive disks (RAID) in a variety of configurations to \nensure that we do not lose data from hardware failures in individual disks, we can replicate \ndata from one machine to another over a network, or we can make copies of data onto backup \nstorage media, such as DVDs or magnetic tapes.  \n4.2.4 Protecting equipment  \n\u2022 Last on the list of our concerns for physical security, although still very important and \nsignificant, is protecting our equipment, and, to a certain extent, the facilities that house it.  \n\u2022 This category falls last on the list because it represents the easiest and cheapest segment of \nour assets to replace.  \n\u2022 Even in the case of a major disaster that completely destroys our facility and all the computing \nequipment inside it, as long as we still have the people needed to run our operation and are \nable to restore or access our critical data, we can be back in working order very shortly.  \n\u2022 Replacing floor space or relocating to another area nearby can generally be accomplished \nwith relative ease, and computing equipment is both cheap and plentiful.  \n\u2022 Although it may take us some time to be back to the same state we were in before the incident, \ngetting to a bare minimum working state technology-wise is often a simple, if arduous, task. \n \n(a) Physical Concerns for Equipment \n\u2022 The physical threats that might harm our equipment, although fewer than those we might find \nharmful to people, are still numerous.  \n\u2022 Extreme temperatures can be very harmful to equipment. We typically think of heat as being \nthe most harmful to computing equipment, and this is largely correct.  \n\u2022 In environments that contain large numbers of computers and associated equipment, such as \nin a data centre, we rely on environmental conditioning equipment to keep the temperature \ndown to a reasonable level, typically in the high-60s to mid-70s on the Fahrenheit scale, \nalthough there is some debate over the subject.", "chunk_id": "62a2d67b-2539-4393-b156-231b95452483", "chroma:document": "\u2022 Even in the case of a major disaster that completely destroys our facility and all the computing \nequipment inside it, as long as we still have the people needed to run our operation and are \nable to restore or access our critical data, we can be back in working order very shortly.  \n\u2022 Replacing floor space or relocating to another area nearby can generally be accomplished"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: f2af2bfd-6c2b-471b-bff0-7138e59621d2
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 149, "full_page_content": "150 \n \n(d) Backups  \n\u2022 In order to ensure that we can maintain the availability of our data, we will likely want to \nmaintain backups.  \n\u2022 Not only do we need to back up the data itself, but we also need to maintain backups of the \nequipment and infrastructure that are used to provide access to the data. We can perform data \nbackups in a number of ways.  \n\u2022 We can utilize redundant arrays of inexpensive disks (RAID) in a variety of configurations to \nensure that we do not lose data from hardware failures in individual disks, we can replicate \ndata from one machine to another over a network, or we can make copies of data onto backup \nstorage media, such as DVDs or magnetic tapes.  \n4.2.4 Protecting equipment  \n\u2022 Last on the list of our concerns for physical security, although still very important and \nsignificant, is protecting our equipment, and, to a certain extent, the facilities that house it.  \n\u2022 This category falls last on the list because it represents the easiest and cheapest segment of \nour assets to replace.  \n\u2022 Even in the case of a major disaster that completely destroys our facility and all the computing \nequipment inside it, as long as we still have the people needed to run our operation and are \nable to restore or access our critical data, we can be back in working order very shortly.  \n\u2022 Replacing floor space or relocating to another area nearby can generally be accomplished \nwith relative ease, and computing equipment is both cheap and plentiful.  \n\u2022 Although it may take us some time to be back to the same state we were in before the incident, \ngetting to a bare minimum working state technology-wise is often a simple, if arduous, task. \n \n(a) Physical Concerns for Equipment \n\u2022 The physical threats that might harm our equipment, although fewer than those we might find \nharmful to people, are still numerous.  \n\u2022 Extreme temperatures can be very harmful to equipment. We typically think of heat as being \nthe most harmful to computing equipment, and this is largely correct.  \n\u2022 In environments that contain large numbers of computers and associated equipment, such as \nin a data centre, we rely on environmental conditioning equipment to keep the temperature \ndown to a reasonable level, typically in the high-60s to mid-70s on the Fahrenheit scale, \nalthough there is some debate over the subject.", "chunk_id": "579bac67-6cb7-4a20-a8ed-7b208692361f", "chroma:document": "with relative ease, and computing equipment is both cheap and plentiful.  \n\u2022 Although it may take us some time to be back to the same state we were in before the incident, \ngetting to a bare minimum working state technology-wise is often a simple, if arduous, task. \n \n(a) Physical Concerns for Equipment"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 00ec017e-1804-48f7-9aa1-9cf99210a850
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 149, "full_page_content": "150 \n \n(d) Backups  \n\u2022 In order to ensure that we can maintain the availability of our data, we will likely want to \nmaintain backups.  \n\u2022 Not only do we need to back up the data itself, but we also need to maintain backups of the \nequipment and infrastructure that are used to provide access to the data. We can perform data \nbackups in a number of ways.  \n\u2022 We can utilize redundant arrays of inexpensive disks (RAID) in a variety of configurations to \nensure that we do not lose data from hardware failures in individual disks, we can replicate \ndata from one machine to another over a network, or we can make copies of data onto backup \nstorage media, such as DVDs or magnetic tapes.  \n4.2.4 Protecting equipment  \n\u2022 Last on the list of our concerns for physical security, although still very important and \nsignificant, is protecting our equipment, and, to a certain extent, the facilities that house it.  \n\u2022 This category falls last on the list because it represents the easiest and cheapest segment of \nour assets to replace.  \n\u2022 Even in the case of a major disaster that completely destroys our facility and all the computing \nequipment inside it, as long as we still have the people needed to run our operation and are \nable to restore or access our critical data, we can be back in working order very shortly.  \n\u2022 Replacing floor space or relocating to another area nearby can generally be accomplished \nwith relative ease, and computing equipment is both cheap and plentiful.  \n\u2022 Although it may take us some time to be back to the same state we were in before the incident, \ngetting to a bare minimum working state technology-wise is often a simple, if arduous, task. \n \n(a) Physical Concerns for Equipment \n\u2022 The physical threats that might harm our equipment, although fewer than those we might find \nharmful to people, are still numerous.  \n\u2022 Extreme temperatures can be very harmful to equipment. We typically think of heat as being \nthe most harmful to computing equipment, and this is largely correct.  \n\u2022 In environments that contain large numbers of computers and associated equipment, such as \nin a data centre, we rely on environmental conditioning equipment to keep the temperature \ndown to a reasonable level, typically in the high-60s to mid-70s on the Fahrenheit scale, \nalthough there is some debate over the subject.", "chunk_id": "5b1d96a4-353d-4e26-ac4b-4267562b7b85", "chroma:document": "\u2022 The physical threats that might harm our equipment, although fewer than those we might find \nharmful to people, are still numerous.  \n\u2022 Extreme temperatures can be very harmful to equipment. We typically think of heat as being \nthe most harmful to computing equipment, and this is largely correct."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: a20b5d74-8f4c-4aae-b58b-53b978216eef
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 149, "full_page_content": "150 \n \n(d) Backups  \n\u2022 In order to ensure that we can maintain the availability of our data, we will likely want to \nmaintain backups.  \n\u2022 Not only do we need to back up the data itself, but we also need to maintain backups of the \nequipment and infrastructure that are used to provide access to the data. We can perform data \nbackups in a number of ways.  \n\u2022 We can utilize redundant arrays of inexpensive disks (RAID) in a variety of configurations to \nensure that we do not lose data from hardware failures in individual disks, we can replicate \ndata from one machine to another over a network, or we can make copies of data onto backup \nstorage media, such as DVDs or magnetic tapes.  \n4.2.4 Protecting equipment  \n\u2022 Last on the list of our concerns for physical security, although still very important and \nsignificant, is protecting our equipment, and, to a certain extent, the facilities that house it.  \n\u2022 This category falls last on the list because it represents the easiest and cheapest segment of \nour assets to replace.  \n\u2022 Even in the case of a major disaster that completely destroys our facility and all the computing \nequipment inside it, as long as we still have the people needed to run our operation and are \nable to restore or access our critical data, we can be back in working order very shortly.  \n\u2022 Replacing floor space or relocating to another area nearby can generally be accomplished \nwith relative ease, and computing equipment is both cheap and plentiful.  \n\u2022 Although it may take us some time to be back to the same state we were in before the incident, \ngetting to a bare minimum working state technology-wise is often a simple, if arduous, task. \n \n(a) Physical Concerns for Equipment \n\u2022 The physical threats that might harm our equipment, although fewer than those we might find \nharmful to people, are still numerous.  \n\u2022 Extreme temperatures can be very harmful to equipment. We typically think of heat as being \nthe most harmful to computing equipment, and this is largely correct.  \n\u2022 In environments that contain large numbers of computers and associated equipment, such as \nin a data centre, we rely on environmental conditioning equipment to keep the temperature \ndown to a reasonable level, typically in the high-60s to mid-70s on the Fahrenheit scale, \nalthough there is some debate over the subject.", "chunk_id": "162b5830-cd83-4e29-a4d2-badea4733efd", "chroma:document": "\u2022 In environments that contain large numbers of computers and associated equipment, such as \nin a data centre, we rely on environmental conditioning equipment to keep the temperature \ndown to a reasonable level, typically in the high-60s to mid-70s on the Fahrenheit scale, \nalthough there is some debate over the subject."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 96186905-8048-4794-b51d-4f18670a3527
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 150, "full_page_content": "151 \n \n\u2022 Liquids can be very harmful to equipment, even when in quantities as small as those that can \nbe found in humid air.  \n\u2022 Depending on the liquid in question, and the quantity of it present, we may find corrosion in \na variety of devices, short circuits in electrical equipment, and other harmful effects.  \n\u2022 Clearly, in extreme cases, such as we might find in flooding, such equipment will often be \nrendered completely unusable after having been immersed.  \n\u2022 Living organisms can also be harmful to equipment, although in the environments with which \nwe will typically be concerned, these will often be of the smaller persuasion.  \n\u2022 Insects and small animals that have gained access to our equipment may cause electrical \nshorts, interfere with cooling fans, chew on wiring, and generally wreak havoc.  \n\u2022 Movement in earth and in the structure of our facilities can be a very bad thing for our \nequipment. One of the more obvious examples we can look at is an earthquake.  \n\u2022 Not only can earthquakes cause structural damage to our facilities, but the resultant shaking, \nvibrations, and potential for impacts due to structural failures can cause a large amount of \ndamage.  \n\u2022 Energy anomalies can be extremely harmful to any type of electrical equipment in a variety \nof ways.  \n\u2022 If we see issues with power being absent or temporarily not sending the expected amount of \nvoltage, our equipment may be damaged beyond repair as a result.  \n\u2022 Good facility design will provide some measure of protection against such threats, but we \ngenerally cannot completely mitigate the effects of severe electrical issues, such as lightning \nstrikes. Smoke and fire are very bad for our equipment, as they introduce a number of harmful \nconditions. With smoke or fire, we might experience extreme temperatures, electrical issues, \nmovement, liquids, and a variety of other problems.  \n\u2022 Efforts to extinguish fires, depending on the methods used, may also cause as much harm as \nthe fire itself.  \n(b) Site Selection \n\u2022 When we are planning a new facility, or selecting a new location to which to move, we should \nbe aware of the area in which the facility will be located.  \n\u2022 A number of factors could cause us issues in terms of protecting our equipment and may \nimpact the safety of our people and data as well.", "chunk_id": "04a83ec4-8398-46c1-948f-f81ee186bb9b", "chroma:document": "151 \n \n\u2022 Liquids can be very harmful to equipment, even when in quantities as small as those that can \nbe found in humid air.  \n\u2022 Depending on the liquid in question, and the quantity of it present, we may find corrosion in \na variety of devices, short circuits in electrical equipment, and other harmful effects."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: b9457f25-0098-4632-b07a-6aefd7115a73
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 150, "full_page_content": "151 \n \n\u2022 Liquids can be very harmful to equipment, even when in quantities as small as those that can \nbe found in humid air.  \n\u2022 Depending on the liquid in question, and the quantity of it present, we may find corrosion in \na variety of devices, short circuits in electrical equipment, and other harmful effects.  \n\u2022 Clearly, in extreme cases, such as we might find in flooding, such equipment will often be \nrendered completely unusable after having been immersed.  \n\u2022 Living organisms can also be harmful to equipment, although in the environments with which \nwe will typically be concerned, these will often be of the smaller persuasion.  \n\u2022 Insects and small animals that have gained access to our equipment may cause electrical \nshorts, interfere with cooling fans, chew on wiring, and generally wreak havoc.  \n\u2022 Movement in earth and in the structure of our facilities can be a very bad thing for our \nequipment. One of the more obvious examples we can look at is an earthquake.  \n\u2022 Not only can earthquakes cause structural damage to our facilities, but the resultant shaking, \nvibrations, and potential for impacts due to structural failures can cause a large amount of \ndamage.  \n\u2022 Energy anomalies can be extremely harmful to any type of electrical equipment in a variety \nof ways.  \n\u2022 If we see issues with power being absent or temporarily not sending the expected amount of \nvoltage, our equipment may be damaged beyond repair as a result.  \n\u2022 Good facility design will provide some measure of protection against such threats, but we \ngenerally cannot completely mitigate the effects of severe electrical issues, such as lightning \nstrikes. Smoke and fire are very bad for our equipment, as they introduce a number of harmful \nconditions. With smoke or fire, we might experience extreme temperatures, electrical issues, \nmovement, liquids, and a variety of other problems.  \n\u2022 Efforts to extinguish fires, depending on the methods used, may also cause as much harm as \nthe fire itself.  \n(b) Site Selection \n\u2022 When we are planning a new facility, or selecting a new location to which to move, we should \nbe aware of the area in which the facility will be located.  \n\u2022 A number of factors could cause us issues in terms of protecting our equipment and may \nimpact the safety of our people and data as well.", "chunk_id": "74ec3338-9386-4b1e-a305-50ef4890ccb9", "chroma:document": "\u2022 Clearly, in extreme cases, such as we might find in flooding, such equipment will often be \nrendered completely unusable after having been immersed.  \n\u2022 Living organisms can also be harmful to equipment, although in the environments with which \nwe will typically be concerned, these will often be of the smaller persuasion."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 93ce067a-6ecf-47da-8d45-deac7183b239
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 150, "full_page_content": "151 \n \n\u2022 Liquids can be very harmful to equipment, even when in quantities as small as those that can \nbe found in humid air.  \n\u2022 Depending on the liquid in question, and the quantity of it present, we may find corrosion in \na variety of devices, short circuits in electrical equipment, and other harmful effects.  \n\u2022 Clearly, in extreme cases, such as we might find in flooding, such equipment will often be \nrendered completely unusable after having been immersed.  \n\u2022 Living organisms can also be harmful to equipment, although in the environments with which \nwe will typically be concerned, these will often be of the smaller persuasion.  \n\u2022 Insects and small animals that have gained access to our equipment may cause electrical \nshorts, interfere with cooling fans, chew on wiring, and generally wreak havoc.  \n\u2022 Movement in earth and in the structure of our facilities can be a very bad thing for our \nequipment. One of the more obvious examples we can look at is an earthquake.  \n\u2022 Not only can earthquakes cause structural damage to our facilities, but the resultant shaking, \nvibrations, and potential for impacts due to structural failures can cause a large amount of \ndamage.  \n\u2022 Energy anomalies can be extremely harmful to any type of electrical equipment in a variety \nof ways.  \n\u2022 If we see issues with power being absent or temporarily not sending the expected amount of \nvoltage, our equipment may be damaged beyond repair as a result.  \n\u2022 Good facility design will provide some measure of protection against such threats, but we \ngenerally cannot completely mitigate the effects of severe electrical issues, such as lightning \nstrikes. Smoke and fire are very bad for our equipment, as they introduce a number of harmful \nconditions. With smoke or fire, we might experience extreme temperatures, electrical issues, \nmovement, liquids, and a variety of other problems.  \n\u2022 Efforts to extinguish fires, depending on the methods used, may also cause as much harm as \nthe fire itself.  \n(b) Site Selection \n\u2022 When we are planning a new facility, or selecting a new location to which to move, we should \nbe aware of the area in which the facility will be located.  \n\u2022 A number of factors could cause us issues in terms of protecting our equipment and may \nimpact the safety of our people and data as well.", "chunk_id": "74f94b41-f1e3-4069-9671-e2f39704eb27", "chroma:document": "\u2022 Insects and small animals that have gained access to our equipment may cause electrical \nshorts, interfere with cooling fans, chew on wiring, and generally wreak havoc.  \n\u2022 Movement in earth and in the structure of our facilities can be a very bad thing for our \nequipment. One of the more obvious examples we can look at is an earthquake."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: dd3d3831-94d6-4c68-8e7c-895089d07014
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 150, "full_page_content": "151 \n \n\u2022 Liquids can be very harmful to equipment, even when in quantities as small as those that can \nbe found in humid air.  \n\u2022 Depending on the liquid in question, and the quantity of it present, we may find corrosion in \na variety of devices, short circuits in electrical equipment, and other harmful effects.  \n\u2022 Clearly, in extreme cases, such as we might find in flooding, such equipment will often be \nrendered completely unusable after having been immersed.  \n\u2022 Living organisms can also be harmful to equipment, although in the environments with which \nwe will typically be concerned, these will often be of the smaller persuasion.  \n\u2022 Insects and small animals that have gained access to our equipment may cause electrical \nshorts, interfere with cooling fans, chew on wiring, and generally wreak havoc.  \n\u2022 Movement in earth and in the structure of our facilities can be a very bad thing for our \nequipment. One of the more obvious examples we can look at is an earthquake.  \n\u2022 Not only can earthquakes cause structural damage to our facilities, but the resultant shaking, \nvibrations, and potential for impacts due to structural failures can cause a large amount of \ndamage.  \n\u2022 Energy anomalies can be extremely harmful to any type of electrical equipment in a variety \nof ways.  \n\u2022 If we see issues with power being absent or temporarily not sending the expected amount of \nvoltage, our equipment may be damaged beyond repair as a result.  \n\u2022 Good facility design will provide some measure of protection against such threats, but we \ngenerally cannot completely mitigate the effects of severe electrical issues, such as lightning \nstrikes. Smoke and fire are very bad for our equipment, as they introduce a number of harmful \nconditions. With smoke or fire, we might experience extreme temperatures, electrical issues, \nmovement, liquids, and a variety of other problems.  \n\u2022 Efforts to extinguish fires, depending on the methods used, may also cause as much harm as \nthe fire itself.  \n(b) Site Selection \n\u2022 When we are planning a new facility, or selecting a new location to which to move, we should \nbe aware of the area in which the facility will be located.  \n\u2022 A number of factors could cause us issues in terms of protecting our equipment and may \nimpact the safety of our people and data as well.", "chunk_id": "9ca4d240-6356-4571-9d6d-92254dc9b078", "chroma:document": "\u2022 Not only can earthquakes cause structural damage to our facilities, but the resultant shaking, \nvibrations, and potential for impacts due to structural failures can cause a large amount of \ndamage.  \n\u2022 Energy anomalies can be extremely harmful to any type of electrical equipment in a variety \nof ways."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: e38c3771-aa05-42dd-a6f9-5b984ae8c162
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 150, "full_page_content": "151 \n \n\u2022 Liquids can be very harmful to equipment, even when in quantities as small as those that can \nbe found in humid air.  \n\u2022 Depending on the liquid in question, and the quantity of it present, we may find corrosion in \na variety of devices, short circuits in electrical equipment, and other harmful effects.  \n\u2022 Clearly, in extreme cases, such as we might find in flooding, such equipment will often be \nrendered completely unusable after having been immersed.  \n\u2022 Living organisms can also be harmful to equipment, although in the environments with which \nwe will typically be concerned, these will often be of the smaller persuasion.  \n\u2022 Insects and small animals that have gained access to our equipment may cause electrical \nshorts, interfere with cooling fans, chew on wiring, and generally wreak havoc.  \n\u2022 Movement in earth and in the structure of our facilities can be a very bad thing for our \nequipment. One of the more obvious examples we can look at is an earthquake.  \n\u2022 Not only can earthquakes cause structural damage to our facilities, but the resultant shaking, \nvibrations, and potential for impacts due to structural failures can cause a large amount of \ndamage.  \n\u2022 Energy anomalies can be extremely harmful to any type of electrical equipment in a variety \nof ways.  \n\u2022 If we see issues with power being absent or temporarily not sending the expected amount of \nvoltage, our equipment may be damaged beyond repair as a result.  \n\u2022 Good facility design will provide some measure of protection against such threats, but we \ngenerally cannot completely mitigate the effects of severe electrical issues, such as lightning \nstrikes. Smoke and fire are very bad for our equipment, as they introduce a number of harmful \nconditions. With smoke or fire, we might experience extreme temperatures, electrical issues, \nmovement, liquids, and a variety of other problems.  \n\u2022 Efforts to extinguish fires, depending on the methods used, may also cause as much harm as \nthe fire itself.  \n(b) Site Selection \n\u2022 When we are planning a new facility, or selecting a new location to which to move, we should \nbe aware of the area in which the facility will be located.  \n\u2022 A number of factors could cause us issues in terms of protecting our equipment and may \nimpact the safety of our people and data as well.", "chunk_id": "5a0e81ad-3bc8-4497-bb68-9d0c167c01a6", "chroma:document": "of ways.  \n\u2022 If we see issues with power being absent or temporarily not sending the expected amount of \nvoltage, our equipment may be damaged beyond repair as a result.  \n\u2022 Good facility design will provide some measure of protection against such threats, but we \ngenerally cannot completely mitigate the effects of severe electrical issues, such as lightning"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 4fcca30c-bc97-49b1-aa34-cae2cb68667c
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 150, "full_page_content": "151 \n \n\u2022 Liquids can be very harmful to equipment, even when in quantities as small as those that can \nbe found in humid air.  \n\u2022 Depending on the liquid in question, and the quantity of it present, we may find corrosion in \na variety of devices, short circuits in electrical equipment, and other harmful effects.  \n\u2022 Clearly, in extreme cases, such as we might find in flooding, such equipment will often be \nrendered completely unusable after having been immersed.  \n\u2022 Living organisms can also be harmful to equipment, although in the environments with which \nwe will typically be concerned, these will often be of the smaller persuasion.  \n\u2022 Insects and small animals that have gained access to our equipment may cause electrical \nshorts, interfere with cooling fans, chew on wiring, and generally wreak havoc.  \n\u2022 Movement in earth and in the structure of our facilities can be a very bad thing for our \nequipment. One of the more obvious examples we can look at is an earthquake.  \n\u2022 Not only can earthquakes cause structural damage to our facilities, but the resultant shaking, \nvibrations, and potential for impacts due to structural failures can cause a large amount of \ndamage.  \n\u2022 Energy anomalies can be extremely harmful to any type of electrical equipment in a variety \nof ways.  \n\u2022 If we see issues with power being absent or temporarily not sending the expected amount of \nvoltage, our equipment may be damaged beyond repair as a result.  \n\u2022 Good facility design will provide some measure of protection against such threats, but we \ngenerally cannot completely mitigate the effects of severe electrical issues, such as lightning \nstrikes. Smoke and fire are very bad for our equipment, as they introduce a number of harmful \nconditions. With smoke or fire, we might experience extreme temperatures, electrical issues, \nmovement, liquids, and a variety of other problems.  \n\u2022 Efforts to extinguish fires, depending on the methods used, may also cause as much harm as \nthe fire itself.  \n(b) Site Selection \n\u2022 When we are planning a new facility, or selecting a new location to which to move, we should \nbe aware of the area in which the facility will be located.  \n\u2022 A number of factors could cause us issues in terms of protecting our equipment and may \nimpact the safety of our people and data as well.", "chunk_id": "444c8e17-60db-44f2-8d69-5e14c34e8846", "chroma:document": "strikes. Smoke and fire are very bad for our equipment, as they introduce a number of harmful \nconditions. With smoke or fire, we might experience extreme temperatures, electrical issues, \nmovement, liquids, and a variety of other problems.  \n\u2022 Efforts to extinguish fires, depending on the methods used, may also cause as much harm as \nthe fire itself.  \n(b) Site Selection"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: d5701ef6-ceae-4f46-927d-accde99b1331
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 150, "full_page_content": "151 \n \n\u2022 Liquids can be very harmful to equipment, even when in quantities as small as those that can \nbe found in humid air.  \n\u2022 Depending on the liquid in question, and the quantity of it present, we may find corrosion in \na variety of devices, short circuits in electrical equipment, and other harmful effects.  \n\u2022 Clearly, in extreme cases, such as we might find in flooding, such equipment will often be \nrendered completely unusable after having been immersed.  \n\u2022 Living organisms can also be harmful to equipment, although in the environments with which \nwe will typically be concerned, these will often be of the smaller persuasion.  \n\u2022 Insects and small animals that have gained access to our equipment may cause electrical \nshorts, interfere with cooling fans, chew on wiring, and generally wreak havoc.  \n\u2022 Movement in earth and in the structure of our facilities can be a very bad thing for our \nequipment. One of the more obvious examples we can look at is an earthquake.  \n\u2022 Not only can earthquakes cause structural damage to our facilities, but the resultant shaking, \nvibrations, and potential for impacts due to structural failures can cause a large amount of \ndamage.  \n\u2022 Energy anomalies can be extremely harmful to any type of electrical equipment in a variety \nof ways.  \n\u2022 If we see issues with power being absent or temporarily not sending the expected amount of \nvoltage, our equipment may be damaged beyond repair as a result.  \n\u2022 Good facility design will provide some measure of protection against such threats, but we \ngenerally cannot completely mitigate the effects of severe electrical issues, such as lightning \nstrikes. Smoke and fire are very bad for our equipment, as they introduce a number of harmful \nconditions. With smoke or fire, we might experience extreme temperatures, electrical issues, \nmovement, liquids, and a variety of other problems.  \n\u2022 Efforts to extinguish fires, depending on the methods used, may also cause as much harm as \nthe fire itself.  \n(b) Site Selection \n\u2022 When we are planning a new facility, or selecting a new location to which to move, we should \nbe aware of the area in which the facility will be located.  \n\u2022 A number of factors could cause us issues in terms of protecting our equipment and may \nimpact the safety of our people and data as well.", "chunk_id": "56d19824-0f75-433c-8e70-5854409fb9fd", "chroma:document": "(b) Site Selection \n\u2022 When we are planning a new facility, or selecting a new location to which to move, we should \nbe aware of the area in which the facility will be located.  \n\u2022 A number of factors could cause us issues in terms of protecting our equipment and may \nimpact the safety of our people and data as well."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: cb18b38a-722c-478d-b531-71a2546fc5ec
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 151, "full_page_content": "152 \n \n\u2022 If the site is located in an area prone to natural disasters such as floods, storms, tornadoes, \nmudslides, or similar issues, we may find our facility to be completely unusable or destroyed \nat some point.  \n\u2022 Similar issues might include areas that have the potential for civil unrest, unstable power or \nutilities, poor network connectivity, extreme temperature conditions, and so forth.  \n\u2022 With the proper facility design, we may be able to compensate for some problems without \ngreat difficulty, by installing power filtering and generators in order to compensate for power \nproblems, for instance, but others, such as the local temperature, we may ultimately not be \nable to mitigate to any great extent.   \n\u2022 Although potential site selection issues may not completely preclude our use of the facility, \nwe should be aware that they may cause us problems and plan for such occurrences. For \ncertain types of facilities, such as data centres, for instance, it may be very important for us \nto have as problem-free of an environment as we can possibly select, and, in the case of such \nsite issues, we may want to look elsewhere.  \n(c) Securing Access  \n\u2022 When we discuss securing access to our equipment or our facility, we return again to the \nconcept of defense in depth.  \n\u2022 There are multiple areas, inside and outside, where we may want to place a variety of security \nmeasures, depending on the environment.  \n\u2022 A military installation may have the highest level of security available, whereas a small retail \nstore may have the lowest level. We can often see measures for securing physical access \nimplemented on the perimeter of the property on which various facilities sit.  \n\u2022 Very often, we will at least see minimal measures in place to ensure that vehicle traffic is \ncontrolled and does not enter undesirable places. Such measures may take the form of security \nlandscaping. For example, we may see trees, large boulders, large cement planters, and the \nlike placed in front of buildings or next to driveways in order to prevent vehicle entry.  \n\u2022 At more secure facilities, we might see fences, concrete barriers, and other more obvious \nmeasures.  \n\u2022 Such controls are generally in place as deterrents, and may be preventive in nature as well.  \n\u2022 At the facility itself, we will likely see some variety of locks, whether mechanical or electronic \nwith access badges, in place on the doors entering the building.  \n\u2022 A typical arrangement for non-public buildings is for the main entrance of the building to be \nunlocked during business hours and a security guard or receptionist stationed inside.", "chunk_id": "5bea7d84-1636-4579-bf72-a1a72cb4c339", "chroma:document": "152 \n \n\u2022 If the site is located in an area prone to natural disasters such as floods, storms, tornadoes, \nmudslides, or similar issues, we may find our facility to be completely unusable or destroyed \nat some point.  \n\u2022 Similar issues might include areas that have the potential for civil unrest, unstable power or"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 8e0cc653-b36e-4d62-8549-6f46f56521f7
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 151, "full_page_content": "152 \n \n\u2022 If the site is located in an area prone to natural disasters such as floods, storms, tornadoes, \nmudslides, or similar issues, we may find our facility to be completely unusable or destroyed \nat some point.  \n\u2022 Similar issues might include areas that have the potential for civil unrest, unstable power or \nutilities, poor network connectivity, extreme temperature conditions, and so forth.  \n\u2022 With the proper facility design, we may be able to compensate for some problems without \ngreat difficulty, by installing power filtering and generators in order to compensate for power \nproblems, for instance, but others, such as the local temperature, we may ultimately not be \nable to mitigate to any great extent.   \n\u2022 Although potential site selection issues may not completely preclude our use of the facility, \nwe should be aware that they may cause us problems and plan for such occurrences. For \ncertain types of facilities, such as data centres, for instance, it may be very important for us \nto have as problem-free of an environment as we can possibly select, and, in the case of such \nsite issues, we may want to look elsewhere.  \n(c) Securing Access  \n\u2022 When we discuss securing access to our equipment or our facility, we return again to the \nconcept of defense in depth.  \n\u2022 There are multiple areas, inside and outside, where we may want to place a variety of security \nmeasures, depending on the environment.  \n\u2022 A military installation may have the highest level of security available, whereas a small retail \nstore may have the lowest level. We can often see measures for securing physical access \nimplemented on the perimeter of the property on which various facilities sit.  \n\u2022 Very often, we will at least see minimal measures in place to ensure that vehicle traffic is \ncontrolled and does not enter undesirable places. Such measures may take the form of security \nlandscaping. For example, we may see trees, large boulders, large cement planters, and the \nlike placed in front of buildings or next to driveways in order to prevent vehicle entry.  \n\u2022 At more secure facilities, we might see fences, concrete barriers, and other more obvious \nmeasures.  \n\u2022 Such controls are generally in place as deterrents, and may be preventive in nature as well.  \n\u2022 At the facility itself, we will likely see some variety of locks, whether mechanical or electronic \nwith access badges, in place on the doors entering the building.  \n\u2022 A typical arrangement for non-public buildings is for the main entrance of the building to be \nunlocked during business hours and a security guard or receptionist stationed inside.", "chunk_id": "cb2342ff-0db3-4167-8472-f52bb6c1c75b", "chroma:document": "utilities, poor network connectivity, extreme temperature conditions, and so forth.  \n\u2022 With the proper facility design, we may be able to compensate for some problems without \ngreat difficulty, by installing power filtering and generators in order to compensate for power \nproblems, for instance, but others, such as the local temperature, we may ultimately not be"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 5b750dbc-b3f7-4128-9776-544c7b9aca81
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 151, "full_page_content": "152 \n \n\u2022 If the site is located in an area prone to natural disasters such as floods, storms, tornadoes, \nmudslides, or similar issues, we may find our facility to be completely unusable or destroyed \nat some point.  \n\u2022 Similar issues might include areas that have the potential for civil unrest, unstable power or \nutilities, poor network connectivity, extreme temperature conditions, and so forth.  \n\u2022 With the proper facility design, we may be able to compensate for some problems without \ngreat difficulty, by installing power filtering and generators in order to compensate for power \nproblems, for instance, but others, such as the local temperature, we may ultimately not be \nable to mitigate to any great extent.   \n\u2022 Although potential site selection issues may not completely preclude our use of the facility, \nwe should be aware that they may cause us problems and plan for such occurrences. For \ncertain types of facilities, such as data centres, for instance, it may be very important for us \nto have as problem-free of an environment as we can possibly select, and, in the case of such \nsite issues, we may want to look elsewhere.  \n(c) Securing Access  \n\u2022 When we discuss securing access to our equipment or our facility, we return again to the \nconcept of defense in depth.  \n\u2022 There are multiple areas, inside and outside, where we may want to place a variety of security \nmeasures, depending on the environment.  \n\u2022 A military installation may have the highest level of security available, whereas a small retail \nstore may have the lowest level. We can often see measures for securing physical access \nimplemented on the perimeter of the property on which various facilities sit.  \n\u2022 Very often, we will at least see minimal measures in place to ensure that vehicle traffic is \ncontrolled and does not enter undesirable places. Such measures may take the form of security \nlandscaping. For example, we may see trees, large boulders, large cement planters, and the \nlike placed in front of buildings or next to driveways in order to prevent vehicle entry.  \n\u2022 At more secure facilities, we might see fences, concrete barriers, and other more obvious \nmeasures.  \n\u2022 Such controls are generally in place as deterrents, and may be preventive in nature as well.  \n\u2022 At the facility itself, we will likely see some variety of locks, whether mechanical or electronic \nwith access badges, in place on the doors entering the building.  \n\u2022 A typical arrangement for non-public buildings is for the main entrance of the building to be \nunlocked during business hours and a security guard or receptionist stationed inside.", "chunk_id": "f2b1e67c-f6eb-4a91-8859-f664bd695174", "chroma:document": "able to mitigate to any great extent.   \n\u2022 Although potential site selection issues may not completely preclude our use of the facility, \nwe should be aware that they may cause us problems and plan for such occurrences. For \ncertain types of facilities, such as data centres, for instance, it may be very important for us"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 2934f6e5-3fed-449a-b3a7-e89d6025b4e2
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 151, "full_page_content": "152 \n \n\u2022 If the site is located in an area prone to natural disasters such as floods, storms, tornadoes, \nmudslides, or similar issues, we may find our facility to be completely unusable or destroyed \nat some point.  \n\u2022 Similar issues might include areas that have the potential for civil unrest, unstable power or \nutilities, poor network connectivity, extreme temperature conditions, and so forth.  \n\u2022 With the proper facility design, we may be able to compensate for some problems without \ngreat difficulty, by installing power filtering and generators in order to compensate for power \nproblems, for instance, but others, such as the local temperature, we may ultimately not be \nable to mitigate to any great extent.   \n\u2022 Although potential site selection issues may not completely preclude our use of the facility, \nwe should be aware that they may cause us problems and plan for such occurrences. For \ncertain types of facilities, such as data centres, for instance, it may be very important for us \nto have as problem-free of an environment as we can possibly select, and, in the case of such \nsite issues, we may want to look elsewhere.  \n(c) Securing Access  \n\u2022 When we discuss securing access to our equipment or our facility, we return again to the \nconcept of defense in depth.  \n\u2022 There are multiple areas, inside and outside, where we may want to place a variety of security \nmeasures, depending on the environment.  \n\u2022 A military installation may have the highest level of security available, whereas a small retail \nstore may have the lowest level. We can often see measures for securing physical access \nimplemented on the perimeter of the property on which various facilities sit.  \n\u2022 Very often, we will at least see minimal measures in place to ensure that vehicle traffic is \ncontrolled and does not enter undesirable places. Such measures may take the form of security \nlandscaping. For example, we may see trees, large boulders, large cement planters, and the \nlike placed in front of buildings or next to driveways in order to prevent vehicle entry.  \n\u2022 At more secure facilities, we might see fences, concrete barriers, and other more obvious \nmeasures.  \n\u2022 Such controls are generally in place as deterrents, and may be preventive in nature as well.  \n\u2022 At the facility itself, we will likely see some variety of locks, whether mechanical or electronic \nwith access badges, in place on the doors entering the building.  \n\u2022 A typical arrangement for non-public buildings is for the main entrance of the building to be \nunlocked during business hours and a security guard or receptionist stationed inside.", "chunk_id": "65bb002c-be43-4695-bc27-9743ccb1e2bd", "chroma:document": "to have as problem-free of an environment as we can possibly select, and, in the case of such \nsite issues, we may want to look elsewhere.  \n(c) Securing Access  \n\u2022 When we discuss securing access to our equipment or our facility, we return again to the \nconcept of defense in depth.  \n\u2022 There are multiple areas, inside and outside, where we may want to place a variety of security"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 482ff3af-8934-440a-8d6e-4e46c96369d8
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 151, "full_page_content": "152 \n \n\u2022 If the site is located in an area prone to natural disasters such as floods, storms, tornadoes, \nmudslides, or similar issues, we may find our facility to be completely unusable or destroyed \nat some point.  \n\u2022 Similar issues might include areas that have the potential for civil unrest, unstable power or \nutilities, poor network connectivity, extreme temperature conditions, and so forth.  \n\u2022 With the proper facility design, we may be able to compensate for some problems without \ngreat difficulty, by installing power filtering and generators in order to compensate for power \nproblems, for instance, but others, such as the local temperature, we may ultimately not be \nable to mitigate to any great extent.   \n\u2022 Although potential site selection issues may not completely preclude our use of the facility, \nwe should be aware that they may cause us problems and plan for such occurrences. For \ncertain types of facilities, such as data centres, for instance, it may be very important for us \nto have as problem-free of an environment as we can possibly select, and, in the case of such \nsite issues, we may want to look elsewhere.  \n(c) Securing Access  \n\u2022 When we discuss securing access to our equipment or our facility, we return again to the \nconcept of defense in depth.  \n\u2022 There are multiple areas, inside and outside, where we may want to place a variety of security \nmeasures, depending on the environment.  \n\u2022 A military installation may have the highest level of security available, whereas a small retail \nstore may have the lowest level. We can often see measures for securing physical access \nimplemented on the perimeter of the property on which various facilities sit.  \n\u2022 Very often, we will at least see minimal measures in place to ensure that vehicle traffic is \ncontrolled and does not enter undesirable places. Such measures may take the form of security \nlandscaping. For example, we may see trees, large boulders, large cement planters, and the \nlike placed in front of buildings or next to driveways in order to prevent vehicle entry.  \n\u2022 At more secure facilities, we might see fences, concrete barriers, and other more obvious \nmeasures.  \n\u2022 Such controls are generally in place as deterrents, and may be preventive in nature as well.  \n\u2022 At the facility itself, we will likely see some variety of locks, whether mechanical or electronic \nwith access badges, in place on the doors entering the building.  \n\u2022 A typical arrangement for non-public buildings is for the main entrance of the building to be \nunlocked during business hours and a security guard or receptionist stationed inside.", "chunk_id": "1a539fe9-efcc-48ee-9f45-0061226e0102", "chroma:document": "measures, depending on the environment.  \n\u2022 A military installation may have the highest level of security available, whereas a small retail \nstore may have the lowest level. We can often see measures for securing physical access \nimplemented on the perimeter of the property on which various facilities sit."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: f02b91db-6004-4770-b96e-a17f89159d1d
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 151, "full_page_content": "152 \n \n\u2022 If the site is located in an area prone to natural disasters such as floods, storms, tornadoes, \nmudslides, or similar issues, we may find our facility to be completely unusable or destroyed \nat some point.  \n\u2022 Similar issues might include areas that have the potential for civil unrest, unstable power or \nutilities, poor network connectivity, extreme temperature conditions, and so forth.  \n\u2022 With the proper facility design, we may be able to compensate for some problems without \ngreat difficulty, by installing power filtering and generators in order to compensate for power \nproblems, for instance, but others, such as the local temperature, we may ultimately not be \nable to mitigate to any great extent.   \n\u2022 Although potential site selection issues may not completely preclude our use of the facility, \nwe should be aware that they may cause us problems and plan for such occurrences. For \ncertain types of facilities, such as data centres, for instance, it may be very important for us \nto have as problem-free of an environment as we can possibly select, and, in the case of such \nsite issues, we may want to look elsewhere.  \n(c) Securing Access  \n\u2022 When we discuss securing access to our equipment or our facility, we return again to the \nconcept of defense in depth.  \n\u2022 There are multiple areas, inside and outside, where we may want to place a variety of security \nmeasures, depending on the environment.  \n\u2022 A military installation may have the highest level of security available, whereas a small retail \nstore may have the lowest level. We can often see measures for securing physical access \nimplemented on the perimeter of the property on which various facilities sit.  \n\u2022 Very often, we will at least see minimal measures in place to ensure that vehicle traffic is \ncontrolled and does not enter undesirable places. Such measures may take the form of security \nlandscaping. For example, we may see trees, large boulders, large cement planters, and the \nlike placed in front of buildings or next to driveways in order to prevent vehicle entry.  \n\u2022 At more secure facilities, we might see fences, concrete barriers, and other more obvious \nmeasures.  \n\u2022 Such controls are generally in place as deterrents, and may be preventive in nature as well.  \n\u2022 At the facility itself, we will likely see some variety of locks, whether mechanical or electronic \nwith access badges, in place on the doors entering the building.  \n\u2022 A typical arrangement for non-public buildings is for the main entrance of the building to be \nunlocked during business hours and a security guard or receptionist stationed inside.", "chunk_id": "615928a0-c806-4ab0-8339-21ca3cf01dc7", "chroma:document": "\u2022 Very often, we will at least see minimal measures in place to ensure that vehicle traffic is \ncontrolled and does not enter undesirable places. Such measures may take the form of security \nlandscaping. For example, we may see trees, large boulders, large cement planters, and the \nlike placed in front of buildings or next to driveways in order to prevent vehicle entry."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 6ced8540-6144-4085-811c-8f29a57d1916
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 151, "full_page_content": "152 \n \n\u2022 If the site is located in an area prone to natural disasters such as floods, storms, tornadoes, \nmudslides, or similar issues, we may find our facility to be completely unusable or destroyed \nat some point.  \n\u2022 Similar issues might include areas that have the potential for civil unrest, unstable power or \nutilities, poor network connectivity, extreme temperature conditions, and so forth.  \n\u2022 With the proper facility design, we may be able to compensate for some problems without \ngreat difficulty, by installing power filtering and generators in order to compensate for power \nproblems, for instance, but others, such as the local temperature, we may ultimately not be \nable to mitigate to any great extent.   \n\u2022 Although potential site selection issues may not completely preclude our use of the facility, \nwe should be aware that they may cause us problems and plan for such occurrences. For \ncertain types of facilities, such as data centres, for instance, it may be very important for us \nto have as problem-free of an environment as we can possibly select, and, in the case of such \nsite issues, we may want to look elsewhere.  \n(c) Securing Access  \n\u2022 When we discuss securing access to our equipment or our facility, we return again to the \nconcept of defense in depth.  \n\u2022 There are multiple areas, inside and outside, where we may want to place a variety of security \nmeasures, depending on the environment.  \n\u2022 A military installation may have the highest level of security available, whereas a small retail \nstore may have the lowest level. We can often see measures for securing physical access \nimplemented on the perimeter of the property on which various facilities sit.  \n\u2022 Very often, we will at least see minimal measures in place to ensure that vehicle traffic is \ncontrolled and does not enter undesirable places. Such measures may take the form of security \nlandscaping. For example, we may see trees, large boulders, large cement planters, and the \nlike placed in front of buildings or next to driveways in order to prevent vehicle entry.  \n\u2022 At more secure facilities, we might see fences, concrete barriers, and other more obvious \nmeasures.  \n\u2022 Such controls are generally in place as deterrents, and may be preventive in nature as well.  \n\u2022 At the facility itself, we will likely see some variety of locks, whether mechanical or electronic \nwith access badges, in place on the doors entering the building.  \n\u2022 A typical arrangement for non-public buildings is for the main entrance of the building to be \nunlocked during business hours and a security guard or receptionist stationed inside.", "chunk_id": "bf443be2-c4c8-4db8-ab33-3c2753599119", "chroma:document": "\u2022 At more secure facilities, we might see fences, concrete barriers, and other more obvious \nmeasures.  \n\u2022 Such controls are generally in place as deterrents, and may be preventive in nature as well.  \n\u2022 At the facility itself, we will likely see some variety of locks, whether mechanical or electronic \nwith access badges, in place on the doors entering the building."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 1398e7d9-72f4-4fa1-bca6-6668eaa5cccc
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 151, "full_page_content": "152 \n \n\u2022 If the site is located in an area prone to natural disasters such as floods, storms, tornadoes, \nmudslides, or similar issues, we may find our facility to be completely unusable or destroyed \nat some point.  \n\u2022 Similar issues might include areas that have the potential for civil unrest, unstable power or \nutilities, poor network connectivity, extreme temperature conditions, and so forth.  \n\u2022 With the proper facility design, we may be able to compensate for some problems without \ngreat difficulty, by installing power filtering and generators in order to compensate for power \nproblems, for instance, but others, such as the local temperature, we may ultimately not be \nable to mitigate to any great extent.   \n\u2022 Although potential site selection issues may not completely preclude our use of the facility, \nwe should be aware that they may cause us problems and plan for such occurrences. For \ncertain types of facilities, such as data centres, for instance, it may be very important for us \nto have as problem-free of an environment as we can possibly select, and, in the case of such \nsite issues, we may want to look elsewhere.  \n(c) Securing Access  \n\u2022 When we discuss securing access to our equipment or our facility, we return again to the \nconcept of defense in depth.  \n\u2022 There are multiple areas, inside and outside, where we may want to place a variety of security \nmeasures, depending on the environment.  \n\u2022 A military installation may have the highest level of security available, whereas a small retail \nstore may have the lowest level. We can often see measures for securing physical access \nimplemented on the perimeter of the property on which various facilities sit.  \n\u2022 Very often, we will at least see minimal measures in place to ensure that vehicle traffic is \ncontrolled and does not enter undesirable places. Such measures may take the form of security \nlandscaping. For example, we may see trees, large boulders, large cement planters, and the \nlike placed in front of buildings or next to driveways in order to prevent vehicle entry.  \n\u2022 At more secure facilities, we might see fences, concrete barriers, and other more obvious \nmeasures.  \n\u2022 Such controls are generally in place as deterrents, and may be preventive in nature as well.  \n\u2022 At the facility itself, we will likely see some variety of locks, whether mechanical or electronic \nwith access badges, in place on the doors entering the building.  \n\u2022 A typical arrangement for non-public buildings is for the main entrance of the building to be \nunlocked during business hours and a security guard or receptionist stationed inside.", "chunk_id": "0dcbbf80-9955-45ee-a49e-aeb0bba1ab19", "chroma:document": "\u2022 A typical arrangement for non-public buildings is for the main entrance of the building to be \nunlocked during business hours and a security guard or receptionist stationed inside."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 19386140-0cce-41be-a0da-af5dad6341f7
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 152, "full_page_content": "153 \n \n\u2022 In more secure facilities, we are likely to see all doors locked at all times, and a badge or key \nrequired to enter the building.  \n\u2022 Typically, once inside the building, visitors will have limited access to a lobby area, and, \nperhaps, meeting and restrooms, whereas those authorized to enter the rest of the building \nwill use a key or badge to access it.  \n\u2022 Once inside the facility, we will often see a variety of physical access controls, depending on \nthe work and processes being carried out.  \n\u2022 We may see access controls on internal doors or individual floors of the building in order to \nkeep visitors or unauthorized people from freely accessing the entire facility.  \n\u2022 Very often, in the case where computer rooms or data centers are present, access to them will \nbe  estricted to those that specifically need to enter them for business reasons.  \n\u2022 We may also find more complex physical access controls in place in such areas, such as \nbiometric systems.  \n(d) Environmental Conditions \n\u2022 For the equipment within our facilities, maintaining proper environmental conditions can be \ncrucial to continued operations. Computing equipment can be very sensitive to changes in \npower, temperature, and humidity, as well as electromagnetic disturbances.  \n\u2022 Particularly in areas where we have large quantities of equipment, such as we might find in a \ndata center, maintaining the proper conditions can be challenging, to say the least When \nfacilities that will contain equipment sensitive to such conditions are  constructed, they are \noften equipped with the means to provide emergency electrical power, often in the form of \ngenerators, as well as systems that can heat, cool, and moderate the humidity, as required.  \n\u2022 Outside of locations that are so equipped, our equipment will be at considerably greater risk \nof malfunction and damage. Unfortunately, such controls can be prohibitively expensive and \nwe may not find smaller facilities appropriately equipped. \n \nReferences \nJason Andress, Steven Winterfeld, \u201cThe Basics of Information Security\u201d, 2nd Edition, Elsevier, \n2014.", "chunk_id": "e65e4e20-74d0-4ee5-9a4b-5b2fe1dcd5bc", "chroma:document": "153 \n \n\u2022 In more secure facilities, we are likely to see all doors locked at all times, and a badge or key \nrequired to enter the building.  \n\u2022 Typically, once inside the building, visitors will have limited access to a lobby area, and, \nperhaps, meeting and restrooms, whereas those authorized to enter the rest of the building \nwill use a key or badge to access it."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 68da9d52-a4f8-4c76-ba52-926823ff5f01
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 152, "full_page_content": "153 \n \n\u2022 In more secure facilities, we are likely to see all doors locked at all times, and a badge or key \nrequired to enter the building.  \n\u2022 Typically, once inside the building, visitors will have limited access to a lobby area, and, \nperhaps, meeting and restrooms, whereas those authorized to enter the rest of the building \nwill use a key or badge to access it.  \n\u2022 Once inside the facility, we will often see a variety of physical access controls, depending on \nthe work and processes being carried out.  \n\u2022 We may see access controls on internal doors or individual floors of the building in order to \nkeep visitors or unauthorized people from freely accessing the entire facility.  \n\u2022 Very often, in the case where computer rooms or data centers are present, access to them will \nbe  estricted to those that specifically need to enter them for business reasons.  \n\u2022 We may also find more complex physical access controls in place in such areas, such as \nbiometric systems.  \n(d) Environmental Conditions \n\u2022 For the equipment within our facilities, maintaining proper environmental conditions can be \ncrucial to continued operations. Computing equipment can be very sensitive to changes in \npower, temperature, and humidity, as well as electromagnetic disturbances.  \n\u2022 Particularly in areas where we have large quantities of equipment, such as we might find in a \ndata center, maintaining the proper conditions can be challenging, to say the least When \nfacilities that will contain equipment sensitive to such conditions are  constructed, they are \noften equipped with the means to provide emergency electrical power, often in the form of \ngenerators, as well as systems that can heat, cool, and moderate the humidity, as required.  \n\u2022 Outside of locations that are so equipped, our equipment will be at considerably greater risk \nof malfunction and damage. Unfortunately, such controls can be prohibitively expensive and \nwe may not find smaller facilities appropriately equipped. \n \nReferences \nJason Andress, Steven Winterfeld, \u201cThe Basics of Information Security\u201d, 2nd Edition, Elsevier, \n2014.", "chunk_id": "57423350-45d6-4280-9450-d5663d6b245a", "chroma:document": "\u2022 Once inside the facility, we will often see a variety of physical access controls, depending on \nthe work and processes being carried out.  \n\u2022 We may see access controls on internal doors or individual floors of the building in order to \nkeep visitors or unauthorized people from freely accessing the entire facility."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 971de4ae-f0dc-4536-bd78-e6cd1a79ae0b
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 152, "full_page_content": "153 \n \n\u2022 In more secure facilities, we are likely to see all doors locked at all times, and a badge or key \nrequired to enter the building.  \n\u2022 Typically, once inside the building, visitors will have limited access to a lobby area, and, \nperhaps, meeting and restrooms, whereas those authorized to enter the rest of the building \nwill use a key or badge to access it.  \n\u2022 Once inside the facility, we will often see a variety of physical access controls, depending on \nthe work and processes being carried out.  \n\u2022 We may see access controls on internal doors or individual floors of the building in order to \nkeep visitors or unauthorized people from freely accessing the entire facility.  \n\u2022 Very often, in the case where computer rooms or data centers are present, access to them will \nbe  estricted to those that specifically need to enter them for business reasons.  \n\u2022 We may also find more complex physical access controls in place in such areas, such as \nbiometric systems.  \n(d) Environmental Conditions \n\u2022 For the equipment within our facilities, maintaining proper environmental conditions can be \ncrucial to continued operations. Computing equipment can be very sensitive to changes in \npower, temperature, and humidity, as well as electromagnetic disturbances.  \n\u2022 Particularly in areas where we have large quantities of equipment, such as we might find in a \ndata center, maintaining the proper conditions can be challenging, to say the least When \nfacilities that will contain equipment sensitive to such conditions are  constructed, they are \noften equipped with the means to provide emergency electrical power, often in the form of \ngenerators, as well as systems that can heat, cool, and moderate the humidity, as required.  \n\u2022 Outside of locations that are so equipped, our equipment will be at considerably greater risk \nof malfunction and damage. Unfortunately, such controls can be prohibitively expensive and \nwe may not find smaller facilities appropriately equipped. \n \nReferences \nJason Andress, Steven Winterfeld, \u201cThe Basics of Information Security\u201d, 2nd Edition, Elsevier, \n2014.", "chunk_id": "f53999ce-4a01-4491-ac51-d8b5fe81f46c", "chroma:document": "\u2022 Very often, in the case where computer rooms or data centers are present, access to them will \nbe  estricted to those that specifically need to enter them for business reasons.  \n\u2022 We may also find more complex physical access controls in place in such areas, such as \nbiometric systems.  \n(d) Environmental Conditions"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 94b57597-e600-4d0f-9c7e-8013c8d5ad4b
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 152, "full_page_content": "153 \n \n\u2022 In more secure facilities, we are likely to see all doors locked at all times, and a badge or key \nrequired to enter the building.  \n\u2022 Typically, once inside the building, visitors will have limited access to a lobby area, and, \nperhaps, meeting and restrooms, whereas those authorized to enter the rest of the building \nwill use a key or badge to access it.  \n\u2022 Once inside the facility, we will often see a variety of physical access controls, depending on \nthe work and processes being carried out.  \n\u2022 We may see access controls on internal doors or individual floors of the building in order to \nkeep visitors or unauthorized people from freely accessing the entire facility.  \n\u2022 Very often, in the case where computer rooms or data centers are present, access to them will \nbe  estricted to those that specifically need to enter them for business reasons.  \n\u2022 We may also find more complex physical access controls in place in such areas, such as \nbiometric systems.  \n(d) Environmental Conditions \n\u2022 For the equipment within our facilities, maintaining proper environmental conditions can be \ncrucial to continued operations. Computing equipment can be very sensitive to changes in \npower, temperature, and humidity, as well as electromagnetic disturbances.  \n\u2022 Particularly in areas where we have large quantities of equipment, such as we might find in a \ndata center, maintaining the proper conditions can be challenging, to say the least When \nfacilities that will contain equipment sensitive to such conditions are  constructed, they are \noften equipped with the means to provide emergency electrical power, often in the form of \ngenerators, as well as systems that can heat, cool, and moderate the humidity, as required.  \n\u2022 Outside of locations that are so equipped, our equipment will be at considerably greater risk \nof malfunction and damage. Unfortunately, such controls can be prohibitively expensive and \nwe may not find smaller facilities appropriately equipped. \n \nReferences \nJason Andress, Steven Winterfeld, \u201cThe Basics of Information Security\u201d, 2nd Edition, Elsevier, \n2014.", "chunk_id": "9abfc9d3-a3c3-4469-a88c-b0f18608550a", "chroma:document": "\u2022 For the equipment within our facilities, maintaining proper environmental conditions can be \ncrucial to continued operations. Computing equipment can be very sensitive to changes in \npower, temperature, and humidity, as well as electromagnetic disturbances.  \n\u2022 Particularly in areas where we have large quantities of equipment, such as we might find in a"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 41779005-32c0-4b3d-a43c-8e1df2b268b2
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 152, "full_page_content": "153 \n \n\u2022 In more secure facilities, we are likely to see all doors locked at all times, and a badge or key \nrequired to enter the building.  \n\u2022 Typically, once inside the building, visitors will have limited access to a lobby area, and, \nperhaps, meeting and restrooms, whereas those authorized to enter the rest of the building \nwill use a key or badge to access it.  \n\u2022 Once inside the facility, we will often see a variety of physical access controls, depending on \nthe work and processes being carried out.  \n\u2022 We may see access controls on internal doors or individual floors of the building in order to \nkeep visitors or unauthorized people from freely accessing the entire facility.  \n\u2022 Very often, in the case where computer rooms or data centers are present, access to them will \nbe  estricted to those that specifically need to enter them for business reasons.  \n\u2022 We may also find more complex physical access controls in place in such areas, such as \nbiometric systems.  \n(d) Environmental Conditions \n\u2022 For the equipment within our facilities, maintaining proper environmental conditions can be \ncrucial to continued operations. Computing equipment can be very sensitive to changes in \npower, temperature, and humidity, as well as electromagnetic disturbances.  \n\u2022 Particularly in areas where we have large quantities of equipment, such as we might find in a \ndata center, maintaining the proper conditions can be challenging, to say the least When \nfacilities that will contain equipment sensitive to such conditions are  constructed, they are \noften equipped with the means to provide emergency electrical power, often in the form of \ngenerators, as well as systems that can heat, cool, and moderate the humidity, as required.  \n\u2022 Outside of locations that are so equipped, our equipment will be at considerably greater risk \nof malfunction and damage. Unfortunately, such controls can be prohibitively expensive and \nwe may not find smaller facilities appropriately equipped. \n \nReferences \nJason Andress, Steven Winterfeld, \u201cThe Basics of Information Security\u201d, 2nd Edition, Elsevier, \n2014.", "chunk_id": "a86f0dd6-74d5-47fc-a67f-2b11a4ea7b94", "chroma:document": "data center, maintaining the proper conditions can be challenging, to say the least When \nfacilities that will contain equipment sensitive to such conditions are  constructed, they are \noften equipped with the means to provide emergency electrical power, often in the form of \ngenerators, as well as systems that can heat, cool, and moderate the humidity, as required."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 19f53710-f5f5-4018-8a9f-826a17ab8593
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 152, "full_page_content": "153 \n \n\u2022 In more secure facilities, we are likely to see all doors locked at all times, and a badge or key \nrequired to enter the building.  \n\u2022 Typically, once inside the building, visitors will have limited access to a lobby area, and, \nperhaps, meeting and restrooms, whereas those authorized to enter the rest of the building \nwill use a key or badge to access it.  \n\u2022 Once inside the facility, we will often see a variety of physical access controls, depending on \nthe work and processes being carried out.  \n\u2022 We may see access controls on internal doors or individual floors of the building in order to \nkeep visitors or unauthorized people from freely accessing the entire facility.  \n\u2022 Very often, in the case where computer rooms or data centers are present, access to them will \nbe  estricted to those that specifically need to enter them for business reasons.  \n\u2022 We may also find more complex physical access controls in place in such areas, such as \nbiometric systems.  \n(d) Environmental Conditions \n\u2022 For the equipment within our facilities, maintaining proper environmental conditions can be \ncrucial to continued operations. Computing equipment can be very sensitive to changes in \npower, temperature, and humidity, as well as electromagnetic disturbances.  \n\u2022 Particularly in areas where we have large quantities of equipment, such as we might find in a \ndata center, maintaining the proper conditions can be challenging, to say the least When \nfacilities that will contain equipment sensitive to such conditions are  constructed, they are \noften equipped with the means to provide emergency electrical power, often in the form of \ngenerators, as well as systems that can heat, cool, and moderate the humidity, as required.  \n\u2022 Outside of locations that are so equipped, our equipment will be at considerably greater risk \nof malfunction and damage. Unfortunately, such controls can be prohibitively expensive and \nwe may not find smaller facilities appropriately equipped. \n \nReferences \nJason Andress, Steven Winterfeld, \u201cThe Basics of Information Security\u201d, 2nd Edition, Elsevier, \n2014.", "chunk_id": "238c2770-e3ea-4682-8fab-ea3aefc94aac", "chroma:document": "\u2022 Outside of locations that are so equipped, our equipment will be at considerably greater risk \nof malfunction and damage. Unfortunately, such controls can be prohibitively expensive and \nwe may not find smaller facilities appropriately equipped. \n \nReferences \nJason Andress, Steven Winterfeld, \u201cThe Basics of Information Security\u201d, 2nd Edition, Elsevier, \n2014."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 8a773e5f-b331-4056-854b-829a65326e8c
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 153, "full_page_content": "154 \n \n \nSCHOOL OF COMPUTING \nDEPARTMENT OF INFORMATION TECHNOLOGY \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \nUNIT \u2013 V \u2013 Cyber Security \u2013 SITA1602", "chunk_id": "23552022-6136-44ce-b3d6-22c4a31175c0", "chroma:document": "154 \n \n \nSCHOOL OF COMPUTING \nDEPARTMENT OF INFORMATION TECHNOLOGY \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \nUNIT \u2013 V \u2013 Cyber Security \u2013 SITA1602"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 0e6c5e97-b285-4288-9e57-2968adedef83
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 154, "full_page_content": "155 \n \n5. Application Security \n \n \nSoftware Development Vulnerabilities \u2013 Buffer Overflow \u2013 Race Condition \u2013 Web Security \u2013 \nDatabase Security - Tools \nEqually important to ensuring that we can keep attackers from interacting with our networks in an \nunauthorized manner and subverting our operating system security is ensuring that our applications \nare not misused. \n5.1 Software development vulnerabilities  \n\u2022 A number of common software development vulnerabilities can lead to security issues in our \napplications.  \n\u2022 These issues are all well known as being problematic from a security perspective, and the \nreasons the development practices that lead to them should not be used are a frequent topic of \ndiscussion in both the information security and software engineering communities. \n\u2022 The main categories of software development vulnerabilities include buffer overflows, race \nconditions, input validation attacks, authentication attacks, authorization attacks, and \ncryptographic attacks.  \n\u2022 All these vulnerabilities can be avoided with relative ease when developing new software by \nsimply not using the particular programming techniques that enable them to exist. \n \nFig. 1 Main Software Development Vulnerabilities \n5.2 Buffer Overflows \n\u2022 Buffer overflows, also referred to as buffer overruns, occur when we do not properly account \nfor the size of the data input into our applications.", "chunk_id": "5c1213ad-aed6-4906-92be-741ee8bc062c", "chroma:document": "155 \n \n5. Application Security \n \n \nSoftware Development Vulnerabilities \u2013 Buffer Overflow \u2013 Race Condition \u2013 Web Security \u2013 \nDatabase Security - Tools \nEqually important to ensuring that we can keep attackers from interacting with our networks in an \nunauthorized manner and subverting our operating system security is ensuring that our applications \nare not misused."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: c302ffff-73ed-4271-aa87-afd9c7eda0a4
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 154, "full_page_content": "155 \n \n5. Application Security \n \n \nSoftware Development Vulnerabilities \u2013 Buffer Overflow \u2013 Race Condition \u2013 Web Security \u2013 \nDatabase Security - Tools \nEqually important to ensuring that we can keep attackers from interacting with our networks in an \nunauthorized manner and subverting our operating system security is ensuring that our applications \nare not misused. \n5.1 Software development vulnerabilities  \n\u2022 A number of common software development vulnerabilities can lead to security issues in our \napplications.  \n\u2022 These issues are all well known as being problematic from a security perspective, and the \nreasons the development practices that lead to them should not be used are a frequent topic of \ndiscussion in both the information security and software engineering communities. \n\u2022 The main categories of software development vulnerabilities include buffer overflows, race \nconditions, input validation attacks, authentication attacks, authorization attacks, and \ncryptographic attacks.  \n\u2022 All these vulnerabilities can be avoided with relative ease when developing new software by \nsimply not using the particular programming techniques that enable them to exist. \n \nFig. 1 Main Software Development Vulnerabilities \n5.2 Buffer Overflows \n\u2022 Buffer overflows, also referred to as buffer overruns, occur when we do not properly account \nfor the size of the data input into our applications.", "chunk_id": "e111c8ea-86b3-4363-94a4-96d1b4fba1ae", "chroma:document": "are not misused. \n5.1 Software development vulnerabilities  \n\u2022 A number of common software development vulnerabilities can lead to security issues in our \napplications.  \n\u2022 These issues are all well known as being problematic from a security perspective, and the \nreasons the development practices that lead to them should not be used are a frequent topic of"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 9055d22d-7791-4588-9dfa-9a01f768d8d6
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 154, "full_page_content": "155 \n \n5. Application Security \n \n \nSoftware Development Vulnerabilities \u2013 Buffer Overflow \u2013 Race Condition \u2013 Web Security \u2013 \nDatabase Security - Tools \nEqually important to ensuring that we can keep attackers from interacting with our networks in an \nunauthorized manner and subverting our operating system security is ensuring that our applications \nare not misused. \n5.1 Software development vulnerabilities  \n\u2022 A number of common software development vulnerabilities can lead to security issues in our \napplications.  \n\u2022 These issues are all well known as being problematic from a security perspective, and the \nreasons the development practices that lead to them should not be used are a frequent topic of \ndiscussion in both the information security and software engineering communities. \n\u2022 The main categories of software development vulnerabilities include buffer overflows, race \nconditions, input validation attacks, authentication attacks, authorization attacks, and \ncryptographic attacks.  \n\u2022 All these vulnerabilities can be avoided with relative ease when developing new software by \nsimply not using the particular programming techniques that enable them to exist. \n \nFig. 1 Main Software Development Vulnerabilities \n5.2 Buffer Overflows \n\u2022 Buffer overflows, also referred to as buffer overruns, occur when we do not properly account \nfor the size of the data input into our applications.", "chunk_id": "5a914a31-bf40-4b84-a6e4-b98841f4e446", "chroma:document": "discussion in both the information security and software engineering communities. \n\u2022 The main categories of software development vulnerabilities include buffer overflows, race \nconditions, input validation attacks, authentication attacks, authorization attacks, and \ncryptographic attacks."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 6971c1ce-4c27-4b1b-b81d-c3f414bf1bfb
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 154, "full_page_content": "155 \n \n5. Application Security \n \n \nSoftware Development Vulnerabilities \u2013 Buffer Overflow \u2013 Race Condition \u2013 Web Security \u2013 \nDatabase Security - Tools \nEqually important to ensuring that we can keep attackers from interacting with our networks in an \nunauthorized manner and subverting our operating system security is ensuring that our applications \nare not misused. \n5.1 Software development vulnerabilities  \n\u2022 A number of common software development vulnerabilities can lead to security issues in our \napplications.  \n\u2022 These issues are all well known as being problematic from a security perspective, and the \nreasons the development practices that lead to them should not be used are a frequent topic of \ndiscussion in both the information security and software engineering communities. \n\u2022 The main categories of software development vulnerabilities include buffer overflows, race \nconditions, input validation attacks, authentication attacks, authorization attacks, and \ncryptographic attacks.  \n\u2022 All these vulnerabilities can be avoided with relative ease when developing new software by \nsimply not using the particular programming techniques that enable them to exist. \n \nFig. 1 Main Software Development Vulnerabilities \n5.2 Buffer Overflows \n\u2022 Buffer overflows, also referred to as buffer overruns, occur when we do not properly account \nfor the size of the data input into our applications.", "chunk_id": "ba3b1581-b067-48cf-8d2e-1ee61f3142a4", "chroma:document": "\u2022 All these vulnerabilities can be avoided with relative ease when developing new software by \nsimply not using the particular programming techniques that enable them to exist. \n \nFig. 1 Main Software Development Vulnerabilities \n5.2 Buffer Overflows \n\u2022 Buffer overflows, also referred to as buffer overruns, occur when we do not properly account"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 4263b719-e5db-4e06-89d8-30bbf10aab1e
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 154, "full_page_content": "155 \n \n5. Application Security \n \n \nSoftware Development Vulnerabilities \u2013 Buffer Overflow \u2013 Race Condition \u2013 Web Security \u2013 \nDatabase Security - Tools \nEqually important to ensuring that we can keep attackers from interacting with our networks in an \nunauthorized manner and subverting our operating system security is ensuring that our applications \nare not misused. \n5.1 Software development vulnerabilities  \n\u2022 A number of common software development vulnerabilities can lead to security issues in our \napplications.  \n\u2022 These issues are all well known as being problematic from a security perspective, and the \nreasons the development practices that lead to them should not be used are a frequent topic of \ndiscussion in both the information security and software engineering communities. \n\u2022 The main categories of software development vulnerabilities include buffer overflows, race \nconditions, input validation attacks, authentication attacks, authorization attacks, and \ncryptographic attacks.  \n\u2022 All these vulnerabilities can be avoided with relative ease when developing new software by \nsimply not using the particular programming techniques that enable them to exist. \n \nFig. 1 Main Software Development Vulnerabilities \n5.2 Buffer Overflows \n\u2022 Buffer overflows, also referred to as buffer overruns, occur when we do not properly account \nfor the size of the data input into our applications.", "chunk_id": "bacc8425-cfaa-4e66-84db-edd25230c3cb", "chroma:document": "for the size of the data input into our applications."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 69327a1e-059f-4c93-86aa-4d34479406e9
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 155, "full_page_content": "156 \n \n\u2022 If we are taking data into an application, most programming languages will require that we \nspecify the amount of data we expect to receive, and set aside storage for that data.  \n\u2022 If we do not set a limit on the amount of data we take in, called bounds checking, we may \nreceive 1,000 characters of input where we had only allocated storage for 50 characters.  \n\u2022 In this case, the excess 950 characters of data may be written over other areas in memory that \nare in use by other applications, or by the operating system itself.  \n\u2022 An attacker might use this technique to allow him to tamper with other applications, or to \ncause the operating system to execute his own commands.  \n\u2022 Proper bounds checking can nullify this type of attack entirely. Depending on the language \nwe choose for the development effort, bounds checking may be implemented automatically, \nas is the case with Java and C#. \n5.3 Race Conditions  \n\u2022 Race conditions occur when multiple processes or multiple threads within a process control \nor share access to a particular resource, and the correct handling of that resource depends on \nthe proper ordering or timing of transactions.  \n\u2022 For example, if we are making a $20 withdrawal from our bank account via an ATM, the \nprocess might go as follows: \n1. Check the account balance ($100) 2. Withdraw funds ($20) 3. Update the account balance ($80) \nIf someone else starts the same process at roughly the same time and tries to make a $30 withdrawal, \nwe might end up with a bit of a problem:  \n1. User 1: Check the account balance ($100) 2.  \n2. User 2: Check the account balance ($100) \n3. 3. User 1: Withdraw funds ($20)  \n4. 4. User 2: Withdraw funds ($30) \n5. 5. User 1: Update the account balance ($80) 6. User 2: Update the account balance ($70) \n\u2022 Because access to the resource, our bank account, is shared, we end up with a balance of $70 \nbeing recorded, where we should see only $50.  \n\u2022 In reality, our bank will have implemented measures to keep this from happening, but this \nillustrates the idea of a race condition. Our two users \u201crace\u201d to access the resource, and \nundesirable conditions occur.  \n\u2022 Race conditions can be very difficult to detect in existing software, as they are hard to \nreproduce.", "chunk_id": "28215ba1-94ae-44ef-b4b3-a6131f98c0f6", "chroma:document": "156 \n \n\u2022 If we are taking data into an application, most programming languages will require that we \nspecify the amount of data we expect to receive, and set aside storage for that data.  \n\u2022 If we do not set a limit on the amount of data we take in, called bounds checking, we may \nreceive 1,000 characters of input where we had only allocated storage for 50 characters."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 3807dd23-f7c4-4e4c-80a6-63a6536d411c
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 155, "full_page_content": "156 \n \n\u2022 If we are taking data into an application, most programming languages will require that we \nspecify the amount of data we expect to receive, and set aside storage for that data.  \n\u2022 If we do not set a limit on the amount of data we take in, called bounds checking, we may \nreceive 1,000 characters of input where we had only allocated storage for 50 characters.  \n\u2022 In this case, the excess 950 characters of data may be written over other areas in memory that \nare in use by other applications, or by the operating system itself.  \n\u2022 An attacker might use this technique to allow him to tamper with other applications, or to \ncause the operating system to execute his own commands.  \n\u2022 Proper bounds checking can nullify this type of attack entirely. Depending on the language \nwe choose for the development effort, bounds checking may be implemented automatically, \nas is the case with Java and C#. \n5.3 Race Conditions  \n\u2022 Race conditions occur when multiple processes or multiple threads within a process control \nor share access to a particular resource, and the correct handling of that resource depends on \nthe proper ordering or timing of transactions.  \n\u2022 For example, if we are making a $20 withdrawal from our bank account via an ATM, the \nprocess might go as follows: \n1. Check the account balance ($100) 2. Withdraw funds ($20) 3. Update the account balance ($80) \nIf someone else starts the same process at roughly the same time and tries to make a $30 withdrawal, \nwe might end up with a bit of a problem:  \n1. User 1: Check the account balance ($100) 2.  \n2. User 2: Check the account balance ($100) \n3. 3. User 1: Withdraw funds ($20)  \n4. 4. User 2: Withdraw funds ($30) \n5. 5. User 1: Update the account balance ($80) 6. User 2: Update the account balance ($70) \n\u2022 Because access to the resource, our bank account, is shared, we end up with a balance of $70 \nbeing recorded, where we should see only $50.  \n\u2022 In reality, our bank will have implemented measures to keep this from happening, but this \nillustrates the idea of a race condition. Our two users \u201crace\u201d to access the resource, and \nundesirable conditions occur.  \n\u2022 Race conditions can be very difficult to detect in existing software, as they are hard to \nreproduce.", "chunk_id": "00353421-f73b-4adc-b7e0-3959f2383ee1", "chroma:document": "\u2022 In this case, the excess 950 characters of data may be written over other areas in memory that \nare in use by other applications, or by the operating system itself.  \n\u2022 An attacker might use this technique to allow him to tamper with other applications, or to \ncause the operating system to execute his own commands."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: cfa563c0-920f-4fbf-b155-6c919f0c15a3
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 155, "full_page_content": "156 \n \n\u2022 If we are taking data into an application, most programming languages will require that we \nspecify the amount of data we expect to receive, and set aside storage for that data.  \n\u2022 If we do not set a limit on the amount of data we take in, called bounds checking, we may \nreceive 1,000 characters of input where we had only allocated storage for 50 characters.  \n\u2022 In this case, the excess 950 characters of data may be written over other areas in memory that \nare in use by other applications, or by the operating system itself.  \n\u2022 An attacker might use this technique to allow him to tamper with other applications, or to \ncause the operating system to execute his own commands.  \n\u2022 Proper bounds checking can nullify this type of attack entirely. Depending on the language \nwe choose for the development effort, bounds checking may be implemented automatically, \nas is the case with Java and C#. \n5.3 Race Conditions  \n\u2022 Race conditions occur when multiple processes or multiple threads within a process control \nor share access to a particular resource, and the correct handling of that resource depends on \nthe proper ordering or timing of transactions.  \n\u2022 For example, if we are making a $20 withdrawal from our bank account via an ATM, the \nprocess might go as follows: \n1. Check the account balance ($100) 2. Withdraw funds ($20) 3. Update the account balance ($80) \nIf someone else starts the same process at roughly the same time and tries to make a $30 withdrawal, \nwe might end up with a bit of a problem:  \n1. User 1: Check the account balance ($100) 2.  \n2. User 2: Check the account balance ($100) \n3. 3. User 1: Withdraw funds ($20)  \n4. 4. User 2: Withdraw funds ($30) \n5. 5. User 1: Update the account balance ($80) 6. User 2: Update the account balance ($70) \n\u2022 Because access to the resource, our bank account, is shared, we end up with a balance of $70 \nbeing recorded, where we should see only $50.  \n\u2022 In reality, our bank will have implemented measures to keep this from happening, but this \nillustrates the idea of a race condition. Our two users \u201crace\u201d to access the resource, and \nundesirable conditions occur.  \n\u2022 Race conditions can be very difficult to detect in existing software, as they are hard to \nreproduce.", "chunk_id": "aab7a260-e2ae-4a66-9b41-4beab62b906a", "chroma:document": "\u2022 Proper bounds checking can nullify this type of attack entirely. Depending on the language \nwe choose for the development effort, bounds checking may be implemented automatically, \nas is the case with Java and C#. \n5.3 Race Conditions  \n\u2022 Race conditions occur when multiple processes or multiple threads within a process control"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 744b1a4b-01b0-4374-b844-dc50b2658f4f
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 155, "full_page_content": "156 \n \n\u2022 If we are taking data into an application, most programming languages will require that we \nspecify the amount of data we expect to receive, and set aside storage for that data.  \n\u2022 If we do not set a limit on the amount of data we take in, called bounds checking, we may \nreceive 1,000 characters of input where we had only allocated storage for 50 characters.  \n\u2022 In this case, the excess 950 characters of data may be written over other areas in memory that \nare in use by other applications, or by the operating system itself.  \n\u2022 An attacker might use this technique to allow him to tamper with other applications, or to \ncause the operating system to execute his own commands.  \n\u2022 Proper bounds checking can nullify this type of attack entirely. Depending on the language \nwe choose for the development effort, bounds checking may be implemented automatically, \nas is the case with Java and C#. \n5.3 Race Conditions  \n\u2022 Race conditions occur when multiple processes or multiple threads within a process control \nor share access to a particular resource, and the correct handling of that resource depends on \nthe proper ordering or timing of transactions.  \n\u2022 For example, if we are making a $20 withdrawal from our bank account via an ATM, the \nprocess might go as follows: \n1. Check the account balance ($100) 2. Withdraw funds ($20) 3. Update the account balance ($80) \nIf someone else starts the same process at roughly the same time and tries to make a $30 withdrawal, \nwe might end up with a bit of a problem:  \n1. User 1: Check the account balance ($100) 2.  \n2. User 2: Check the account balance ($100) \n3. 3. User 1: Withdraw funds ($20)  \n4. 4. User 2: Withdraw funds ($30) \n5. 5. User 1: Update the account balance ($80) 6. User 2: Update the account balance ($70) \n\u2022 Because access to the resource, our bank account, is shared, we end up with a balance of $70 \nbeing recorded, where we should see only $50.  \n\u2022 In reality, our bank will have implemented measures to keep this from happening, but this \nillustrates the idea of a race condition. Our two users \u201crace\u201d to access the resource, and \nundesirable conditions occur.  \n\u2022 Race conditions can be very difficult to detect in existing software, as they are hard to \nreproduce.", "chunk_id": "b1d6ac00-a267-4c9a-86c3-4647781a5ee1", "chroma:document": "or share access to a particular resource, and the correct handling of that resource depends on \nthe proper ordering or timing of transactions.  \n\u2022 For example, if we are making a $20 withdrawal from our bank account via an ATM, the \nprocess might go as follows: \n1. Check the account balance ($100) 2. Withdraw funds ($20) 3. Update the account balance ($80)"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: eec66540-2004-431e-b0a8-da7e4a38c188
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 155, "full_page_content": "156 \n \n\u2022 If we are taking data into an application, most programming languages will require that we \nspecify the amount of data we expect to receive, and set aside storage for that data.  \n\u2022 If we do not set a limit on the amount of data we take in, called bounds checking, we may \nreceive 1,000 characters of input where we had only allocated storage for 50 characters.  \n\u2022 In this case, the excess 950 characters of data may be written over other areas in memory that \nare in use by other applications, or by the operating system itself.  \n\u2022 An attacker might use this technique to allow him to tamper with other applications, or to \ncause the operating system to execute his own commands.  \n\u2022 Proper bounds checking can nullify this type of attack entirely. Depending on the language \nwe choose for the development effort, bounds checking may be implemented automatically, \nas is the case with Java and C#. \n5.3 Race Conditions  \n\u2022 Race conditions occur when multiple processes or multiple threads within a process control \nor share access to a particular resource, and the correct handling of that resource depends on \nthe proper ordering or timing of transactions.  \n\u2022 For example, if we are making a $20 withdrawal from our bank account via an ATM, the \nprocess might go as follows: \n1. Check the account balance ($100) 2. Withdraw funds ($20) 3. Update the account balance ($80) \nIf someone else starts the same process at roughly the same time and tries to make a $30 withdrawal, \nwe might end up with a bit of a problem:  \n1. User 1: Check the account balance ($100) 2.  \n2. User 2: Check the account balance ($100) \n3. 3. User 1: Withdraw funds ($20)  \n4. 4. User 2: Withdraw funds ($30) \n5. 5. User 1: Update the account balance ($80) 6. User 2: Update the account balance ($70) \n\u2022 Because access to the resource, our bank account, is shared, we end up with a balance of $70 \nbeing recorded, where we should see only $50.  \n\u2022 In reality, our bank will have implemented measures to keep this from happening, but this \nillustrates the idea of a race condition. Our two users \u201crace\u201d to access the resource, and \nundesirable conditions occur.  \n\u2022 Race conditions can be very difficult to detect in existing software, as they are hard to \nreproduce.", "chunk_id": "cc42b762-d857-4587-b491-6e8a9fcde5a9", "chroma:document": "If someone else starts the same process at roughly the same time and tries to make a $30 withdrawal, \nwe might end up with a bit of a problem:  \n1. User 1: Check the account balance ($100) 2.  \n2. User 2: Check the account balance ($100) \n3. 3. User 1: Withdraw funds ($20)  \n4. 4. User 2: Withdraw funds ($30)"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: dfe2d674-ad20-4127-a1e7-485c552f73df
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 155, "full_page_content": "156 \n \n\u2022 If we are taking data into an application, most programming languages will require that we \nspecify the amount of data we expect to receive, and set aside storage for that data.  \n\u2022 If we do not set a limit on the amount of data we take in, called bounds checking, we may \nreceive 1,000 characters of input where we had only allocated storage for 50 characters.  \n\u2022 In this case, the excess 950 characters of data may be written over other areas in memory that \nare in use by other applications, or by the operating system itself.  \n\u2022 An attacker might use this technique to allow him to tamper with other applications, or to \ncause the operating system to execute his own commands.  \n\u2022 Proper bounds checking can nullify this type of attack entirely. Depending on the language \nwe choose for the development effort, bounds checking may be implemented automatically, \nas is the case with Java and C#. \n5.3 Race Conditions  \n\u2022 Race conditions occur when multiple processes or multiple threads within a process control \nor share access to a particular resource, and the correct handling of that resource depends on \nthe proper ordering or timing of transactions.  \n\u2022 For example, if we are making a $20 withdrawal from our bank account via an ATM, the \nprocess might go as follows: \n1. Check the account balance ($100) 2. Withdraw funds ($20) 3. Update the account balance ($80) \nIf someone else starts the same process at roughly the same time and tries to make a $30 withdrawal, \nwe might end up with a bit of a problem:  \n1. User 1: Check the account balance ($100) 2.  \n2. User 2: Check the account balance ($100) \n3. 3. User 1: Withdraw funds ($20)  \n4. 4. User 2: Withdraw funds ($30) \n5. 5. User 1: Update the account balance ($80) 6. User 2: Update the account balance ($70) \n\u2022 Because access to the resource, our bank account, is shared, we end up with a balance of $70 \nbeing recorded, where we should see only $50.  \n\u2022 In reality, our bank will have implemented measures to keep this from happening, but this \nillustrates the idea of a race condition. Our two users \u201crace\u201d to access the resource, and \nundesirable conditions occur.  \n\u2022 Race conditions can be very difficult to detect in existing software, as they are hard to \nreproduce.", "chunk_id": "fe9e1edb-6abd-429f-8c4d-d8651c697b66", "chroma:document": "5. 5. User 1: Update the account balance ($80) 6. User 2: Update the account balance ($70) \n\u2022 Because access to the resource, our bank account, is shared, we end up with a balance of $70 \nbeing recorded, where we should see only $50.  \n\u2022 In reality, our bank will have implemented measures to keep this from happening, but this"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 53afafec-74cd-4f76-807d-c656cc842bf2
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 155, "full_page_content": "156 \n \n\u2022 If we are taking data into an application, most programming languages will require that we \nspecify the amount of data we expect to receive, and set aside storage for that data.  \n\u2022 If we do not set a limit on the amount of data we take in, called bounds checking, we may \nreceive 1,000 characters of input where we had only allocated storage for 50 characters.  \n\u2022 In this case, the excess 950 characters of data may be written over other areas in memory that \nare in use by other applications, or by the operating system itself.  \n\u2022 An attacker might use this technique to allow him to tamper with other applications, or to \ncause the operating system to execute his own commands.  \n\u2022 Proper bounds checking can nullify this type of attack entirely. Depending on the language \nwe choose for the development effort, bounds checking may be implemented automatically, \nas is the case with Java and C#. \n5.3 Race Conditions  \n\u2022 Race conditions occur when multiple processes or multiple threads within a process control \nor share access to a particular resource, and the correct handling of that resource depends on \nthe proper ordering or timing of transactions.  \n\u2022 For example, if we are making a $20 withdrawal from our bank account via an ATM, the \nprocess might go as follows: \n1. Check the account balance ($100) 2. Withdraw funds ($20) 3. Update the account balance ($80) \nIf someone else starts the same process at roughly the same time and tries to make a $30 withdrawal, \nwe might end up with a bit of a problem:  \n1. User 1: Check the account balance ($100) 2.  \n2. User 2: Check the account balance ($100) \n3. 3. User 1: Withdraw funds ($20)  \n4. 4. User 2: Withdraw funds ($30) \n5. 5. User 1: Update the account balance ($80) 6. User 2: Update the account balance ($70) \n\u2022 Because access to the resource, our bank account, is shared, we end up with a balance of $70 \nbeing recorded, where we should see only $50.  \n\u2022 In reality, our bank will have implemented measures to keep this from happening, but this \nillustrates the idea of a race condition. Our two users \u201crace\u201d to access the resource, and \nundesirable conditions occur.  \n\u2022 Race conditions can be very difficult to detect in existing software, as they are hard to \nreproduce.", "chunk_id": "cb7319af-7f65-495c-8899-963b231542b8", "chroma:document": "illustrates the idea of a race condition. Our two users \u201crace\u201d to access the resource, and \nundesirable conditions occur.  \n\u2022 Race conditions can be very difficult to detect in existing software, as they are hard to \nreproduce."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 3c4f9710-5dd2-417e-8e30-8bf3b2a1ca1c
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 156, "full_page_content": "157 \n \n\u2022 When we are developing new applications, careful handling of the way we access resources \nto avoid dependencies on timing can generally avoid such issues.  \n5.4 Web security \nAttackers can use an enormous variety of techniques to compromise our machines, steal \nsensitive information, and trick us into carrying out activities without our knowledge. These types of \nattacks divide into two main categories: client-side attacks and server-side attacks. \n5.4.1 Client-Side Attacks \nClient-side attacks take advantage of weaknesses in the software loaded on our clients, or those \nattacks that use social engineering to trick us into going along with the attack. There are a large \nnumber of such attacks that use the Web as an attack vehicle. \n5.4.1.1 Cross-Site Scripting \nCross-site scripting (XSS) is an attack carried out by placing code in the form of a scripting \nlanguage into a Web page, or other media, that is interpreted by a client browser, including Adobe \nFlash animation and some types of video files. When another person views the Web page or media, \nhe or she executes the code automatically, and the attack is carried out.  \n5.4.1.2 Cross-Site Request Forgery \nA cross-site request forgery (XSRF) attack is similar to XSS, in a general sense. In this type \nof attack, the attacker places a link, or links, on a Web page in such a way that they will be \nautomatically executed, in order to initiate a particular activity on another Web page or application \nwhere the user is currently authenticated. For instance, such a link might cause the browser to add \nitems to our shopping cart on Amazon, or transfer money from one bank account to another. If we \nare browsing several pages and are still authenticated to the same page the attack is intended for, we \nmight execute the attack in the background and never know it.  \n5.4.1.3 Clickjacking \nClickjacking is an attack that takes advantage of the graphical display capabilities of our \nbrowser to trick us into clicking on something we might not otherwise. Clickjacking attacks work by \nplacing another layer over the page, or portions of the page, in order to obscure what we are actually \nclicking. For example, the attacker might hide a button that says \u201cbuy now\u201d under another layer with \na button that says \u201cmore information.\u201d \n5.4.1.4 Defense", "chunk_id": "a61cc5b5-04e5-49a0-90ef-e690bd01638f", "chroma:document": "157 \n \n\u2022 When we are developing new applications, careful handling of the way we access resources \nto avoid dependencies on timing can generally avoid such issues.  \n5.4 Web security \nAttackers can use an enormous variety of techniques to compromise our machines, steal \nsensitive information, and trick us into carrying out activities without our knowledge. These types of"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 39c23f93-833a-4085-9b1b-51f6f6ef8258
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 156, "full_page_content": "157 \n \n\u2022 When we are developing new applications, careful handling of the way we access resources \nto avoid dependencies on timing can generally avoid such issues.  \n5.4 Web security \nAttackers can use an enormous variety of techniques to compromise our machines, steal \nsensitive information, and trick us into carrying out activities without our knowledge. These types of \nattacks divide into two main categories: client-side attacks and server-side attacks. \n5.4.1 Client-Side Attacks \nClient-side attacks take advantage of weaknesses in the software loaded on our clients, or those \nattacks that use social engineering to trick us into going along with the attack. There are a large \nnumber of such attacks that use the Web as an attack vehicle. \n5.4.1.1 Cross-Site Scripting \nCross-site scripting (XSS) is an attack carried out by placing code in the form of a scripting \nlanguage into a Web page, or other media, that is interpreted by a client browser, including Adobe \nFlash animation and some types of video files. When another person views the Web page or media, \nhe or she executes the code automatically, and the attack is carried out.  \n5.4.1.2 Cross-Site Request Forgery \nA cross-site request forgery (XSRF) attack is similar to XSS, in a general sense. In this type \nof attack, the attacker places a link, or links, on a Web page in such a way that they will be \nautomatically executed, in order to initiate a particular activity on another Web page or application \nwhere the user is currently authenticated. For instance, such a link might cause the browser to add \nitems to our shopping cart on Amazon, or transfer money from one bank account to another. If we \nare browsing several pages and are still authenticated to the same page the attack is intended for, we \nmight execute the attack in the background and never know it.  \n5.4.1.3 Clickjacking \nClickjacking is an attack that takes advantage of the graphical display capabilities of our \nbrowser to trick us into clicking on something we might not otherwise. Clickjacking attacks work by \nplacing another layer over the page, or portions of the page, in order to obscure what we are actually \nclicking. For example, the attacker might hide a button that says \u201cbuy now\u201d under another layer with \na button that says \u201cmore information.\u201d \n5.4.1.4 Defense", "chunk_id": "d26de16c-074b-4d21-b956-33c8ed2cede5", "chroma:document": "attacks divide into two main categories: client-side attacks and server-side attacks. \n5.4.1 Client-Side Attacks \nClient-side attacks take advantage of weaknesses in the software loaded on our clients, or those \nattacks that use social engineering to trick us into going along with the attack. There are a large \nnumber of such attacks that use the Web as an attack vehicle."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 81283116-1ba4-47b6-9b6a-83f700963186
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 156, "full_page_content": "157 \n \n\u2022 When we are developing new applications, careful handling of the way we access resources \nto avoid dependencies on timing can generally avoid such issues.  \n5.4 Web security \nAttackers can use an enormous variety of techniques to compromise our machines, steal \nsensitive information, and trick us into carrying out activities without our knowledge. These types of \nattacks divide into two main categories: client-side attacks and server-side attacks. \n5.4.1 Client-Side Attacks \nClient-side attacks take advantage of weaknesses in the software loaded on our clients, or those \nattacks that use social engineering to trick us into going along with the attack. There are a large \nnumber of such attacks that use the Web as an attack vehicle. \n5.4.1.1 Cross-Site Scripting \nCross-site scripting (XSS) is an attack carried out by placing code in the form of a scripting \nlanguage into a Web page, or other media, that is interpreted by a client browser, including Adobe \nFlash animation and some types of video files. When another person views the Web page or media, \nhe or she executes the code automatically, and the attack is carried out.  \n5.4.1.2 Cross-Site Request Forgery \nA cross-site request forgery (XSRF) attack is similar to XSS, in a general sense. In this type \nof attack, the attacker places a link, or links, on a Web page in such a way that they will be \nautomatically executed, in order to initiate a particular activity on another Web page or application \nwhere the user is currently authenticated. For instance, such a link might cause the browser to add \nitems to our shopping cart on Amazon, or transfer money from one bank account to another. If we \nare browsing several pages and are still authenticated to the same page the attack is intended for, we \nmight execute the attack in the background and never know it.  \n5.4.1.3 Clickjacking \nClickjacking is an attack that takes advantage of the graphical display capabilities of our \nbrowser to trick us into clicking on something we might not otherwise. Clickjacking attacks work by \nplacing another layer over the page, or portions of the page, in order to obscure what we are actually \nclicking. For example, the attacker might hide a button that says \u201cbuy now\u201d under another layer with \na button that says \u201cmore information.\u201d \n5.4.1.4 Defense", "chunk_id": "52b48f6d-1f52-48fe-8bfc-26f37287a246", "chroma:document": "5.4.1.1 Cross-Site Scripting \nCross-site scripting (XSS) is an attack carried out by placing code in the form of a scripting \nlanguage into a Web page, or other media, that is interpreted by a client browser, including Adobe \nFlash animation and some types of video files. When another person views the Web page or media,"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: dba3519c-c7ba-4525-8fd0-703ab432adc4
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 156, "full_page_content": "157 \n \n\u2022 When we are developing new applications, careful handling of the way we access resources \nto avoid dependencies on timing can generally avoid such issues.  \n5.4 Web security \nAttackers can use an enormous variety of techniques to compromise our machines, steal \nsensitive information, and trick us into carrying out activities without our knowledge. These types of \nattacks divide into two main categories: client-side attacks and server-side attacks. \n5.4.1 Client-Side Attacks \nClient-side attacks take advantage of weaknesses in the software loaded on our clients, or those \nattacks that use social engineering to trick us into going along with the attack. There are a large \nnumber of such attacks that use the Web as an attack vehicle. \n5.4.1.1 Cross-Site Scripting \nCross-site scripting (XSS) is an attack carried out by placing code in the form of a scripting \nlanguage into a Web page, or other media, that is interpreted by a client browser, including Adobe \nFlash animation and some types of video files. When another person views the Web page or media, \nhe or she executes the code automatically, and the attack is carried out.  \n5.4.1.2 Cross-Site Request Forgery \nA cross-site request forgery (XSRF) attack is similar to XSS, in a general sense. In this type \nof attack, the attacker places a link, or links, on a Web page in such a way that they will be \nautomatically executed, in order to initiate a particular activity on another Web page or application \nwhere the user is currently authenticated. For instance, such a link might cause the browser to add \nitems to our shopping cart on Amazon, or transfer money from one bank account to another. If we \nare browsing several pages and are still authenticated to the same page the attack is intended for, we \nmight execute the attack in the background and never know it.  \n5.4.1.3 Clickjacking \nClickjacking is an attack that takes advantage of the graphical display capabilities of our \nbrowser to trick us into clicking on something we might not otherwise. Clickjacking attacks work by \nplacing another layer over the page, or portions of the page, in order to obscure what we are actually \nclicking. For example, the attacker might hide a button that says \u201cbuy now\u201d under another layer with \na button that says \u201cmore information.\u201d \n5.4.1.4 Defense", "chunk_id": "4f8f871f-e641-4271-8023-4dc0c481bcef", "chroma:document": "he or she executes the code automatically, and the attack is carried out.  \n5.4.1.2 Cross-Site Request Forgery \nA cross-site request forgery (XSRF) attack is similar to XSS, in a general sense. In this type \nof attack, the attacker places a link, or links, on a Web page in such a way that they will be"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 042dae38-3f30-4113-9b96-c0f025e4295e
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 156, "full_page_content": "157 \n \n\u2022 When we are developing new applications, careful handling of the way we access resources \nto avoid dependencies on timing can generally avoid such issues.  \n5.4 Web security \nAttackers can use an enormous variety of techniques to compromise our machines, steal \nsensitive information, and trick us into carrying out activities without our knowledge. These types of \nattacks divide into two main categories: client-side attacks and server-side attacks. \n5.4.1 Client-Side Attacks \nClient-side attacks take advantage of weaknesses in the software loaded on our clients, or those \nattacks that use social engineering to trick us into going along with the attack. There are a large \nnumber of such attacks that use the Web as an attack vehicle. \n5.4.1.1 Cross-Site Scripting \nCross-site scripting (XSS) is an attack carried out by placing code in the form of a scripting \nlanguage into a Web page, or other media, that is interpreted by a client browser, including Adobe \nFlash animation and some types of video files. When another person views the Web page or media, \nhe or she executes the code automatically, and the attack is carried out.  \n5.4.1.2 Cross-Site Request Forgery \nA cross-site request forgery (XSRF) attack is similar to XSS, in a general sense. In this type \nof attack, the attacker places a link, or links, on a Web page in such a way that they will be \nautomatically executed, in order to initiate a particular activity on another Web page or application \nwhere the user is currently authenticated. For instance, such a link might cause the browser to add \nitems to our shopping cart on Amazon, or transfer money from one bank account to another. If we \nare browsing several pages and are still authenticated to the same page the attack is intended for, we \nmight execute the attack in the background and never know it.  \n5.4.1.3 Clickjacking \nClickjacking is an attack that takes advantage of the graphical display capabilities of our \nbrowser to trick us into clicking on something we might not otherwise. Clickjacking attacks work by \nplacing another layer over the page, or portions of the page, in order to obscure what we are actually \nclicking. For example, the attacker might hide a button that says \u201cbuy now\u201d under another layer with \na button that says \u201cmore information.\u201d \n5.4.1.4 Defense", "chunk_id": "6fd6be75-9d70-4627-91cb-f10c963a9f43", "chroma:document": "automatically executed, in order to initiate a particular activity on another Web page or application \nwhere the user is currently authenticated. For instance, such a link might cause the browser to add \nitems to our shopping cart on Amazon, or transfer money from one bank account to another. If we"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: b8457480-f283-44c0-8bfb-73217c2aabaa
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 156, "full_page_content": "157 \n \n\u2022 When we are developing new applications, careful handling of the way we access resources \nto avoid dependencies on timing can generally avoid such issues.  \n5.4 Web security \nAttackers can use an enormous variety of techniques to compromise our machines, steal \nsensitive information, and trick us into carrying out activities without our knowledge. These types of \nattacks divide into two main categories: client-side attacks and server-side attacks. \n5.4.1 Client-Side Attacks \nClient-side attacks take advantage of weaknesses in the software loaded on our clients, or those \nattacks that use social engineering to trick us into going along with the attack. There are a large \nnumber of such attacks that use the Web as an attack vehicle. \n5.4.1.1 Cross-Site Scripting \nCross-site scripting (XSS) is an attack carried out by placing code in the form of a scripting \nlanguage into a Web page, or other media, that is interpreted by a client browser, including Adobe \nFlash animation and some types of video files. When another person views the Web page or media, \nhe or she executes the code automatically, and the attack is carried out.  \n5.4.1.2 Cross-Site Request Forgery \nA cross-site request forgery (XSRF) attack is similar to XSS, in a general sense. In this type \nof attack, the attacker places a link, or links, on a Web page in such a way that they will be \nautomatically executed, in order to initiate a particular activity on another Web page or application \nwhere the user is currently authenticated. For instance, such a link might cause the browser to add \nitems to our shopping cart on Amazon, or transfer money from one bank account to another. If we \nare browsing several pages and are still authenticated to the same page the attack is intended for, we \nmight execute the attack in the background and never know it.  \n5.4.1.3 Clickjacking \nClickjacking is an attack that takes advantage of the graphical display capabilities of our \nbrowser to trick us into clicking on something we might not otherwise. Clickjacking attacks work by \nplacing another layer over the page, or portions of the page, in order to obscure what we are actually \nclicking. For example, the attacker might hide a button that says \u201cbuy now\u201d under another layer with \na button that says \u201cmore information.\u201d \n5.4.1.4 Defense", "chunk_id": "6bfb02f6-bc7b-42ee-86ab-6bba1a4cdec2", "chroma:document": "are browsing several pages and are still authenticated to the same page the attack is intended for, we \nmight execute the attack in the background and never know it.  \n5.4.1.3 Clickjacking \nClickjacking is an attack that takes advantage of the graphical display capabilities of our \nbrowser to trick us into clicking on something we might not otherwise. Clickjacking attacks work by"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 47077d94-dff7-4d1f-a2d4-3c65bae7a7dc
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 156, "full_page_content": "157 \n \n\u2022 When we are developing new applications, careful handling of the way we access resources \nto avoid dependencies on timing can generally avoid such issues.  \n5.4 Web security \nAttackers can use an enormous variety of techniques to compromise our machines, steal \nsensitive information, and trick us into carrying out activities without our knowledge. These types of \nattacks divide into two main categories: client-side attacks and server-side attacks. \n5.4.1 Client-Side Attacks \nClient-side attacks take advantage of weaknesses in the software loaded on our clients, or those \nattacks that use social engineering to trick us into going along with the attack. There are a large \nnumber of such attacks that use the Web as an attack vehicle. \n5.4.1.1 Cross-Site Scripting \nCross-site scripting (XSS) is an attack carried out by placing code in the form of a scripting \nlanguage into a Web page, or other media, that is interpreted by a client browser, including Adobe \nFlash animation and some types of video files. When another person views the Web page or media, \nhe or she executes the code automatically, and the attack is carried out.  \n5.4.1.2 Cross-Site Request Forgery \nA cross-site request forgery (XSRF) attack is similar to XSS, in a general sense. In this type \nof attack, the attacker places a link, or links, on a Web page in such a way that they will be \nautomatically executed, in order to initiate a particular activity on another Web page or application \nwhere the user is currently authenticated. For instance, such a link might cause the browser to add \nitems to our shopping cart on Amazon, or transfer money from one bank account to another. If we \nare browsing several pages and are still authenticated to the same page the attack is intended for, we \nmight execute the attack in the background and never know it.  \n5.4.1.3 Clickjacking \nClickjacking is an attack that takes advantage of the graphical display capabilities of our \nbrowser to trick us into clicking on something we might not otherwise. Clickjacking attacks work by \nplacing another layer over the page, or portions of the page, in order to obscure what we are actually \nclicking. For example, the attacker might hide a button that says \u201cbuy now\u201d under another layer with \na button that says \u201cmore information.\u201d \n5.4.1.4 Defense", "chunk_id": "312f534a-d6ee-4a42-8e29-36c221616a96", "chroma:document": "placing another layer over the page, or portions of the page, in order to obscure what we are actually \nclicking. For example, the attacker might hide a button that says \u201cbuy now\u201d under another layer with \na button that says \u201cmore information.\u201d \n5.4.1.4 Defense"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 31d4ddd6-b93b-4e93-800e-a17aee8dfb31
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 157, "full_page_content": "158 \n \nThese types of attacks are, for the most part, thwarted by the newer versions of the common \nbrowsers, such as Internet Explorer, Firefox, Safari, and Chrome. In many cases, however, new attack \nvectors are simply variations of old attacks. Additionally, there are innumerable vulnerable clients \nrunning on outdated or unpatched software that are still vulnerable to attacks that are years old. \n5.4.2 Server-Side Attacks \nOn the server side of the Web transaction, a number of vulnerabilities may cause us problems \nas well. Such threats and vulnerabilities can vary widely depending on our operating system, Web \nserver software, various software versions, scripting languages, and many other factors.  \n5.4.2.1 Lack of Input Validation \nSQL injection gives us a strong example of what might happen if we do not properly validate \nthe input of our Web applications. Structured Query Language (SQL) is the language we use to \ncommunicate with many of the common databases on the market today. In the case of databases \nconnected to Web applications, entering specially crafted data into the Web forms that interact with \nthem can sometimes produce results not anticipated by the application developers.  \n5.4.2.2 Improper or Inadequate Permissions \nInadequate permissions can often cause us problems with Web applications, and Internet-\nfacing applications of most any kind. Particularly with Web applications and pages, there are often \nsensitive files and directories that will cause security issues if they are exposed to general users. One \narea that might cause us trouble is the exposure of configuration files.  \nFor example, in many Web applications that make use of a database (that is a vast majority \nof them), there are configuration files that hold the credentials the application uses to access the \ndatabase. If these files and the directories that hold them are not properly secured, an attacker may \nsimply read our credentials from the file and access the database as he or she pleases. For applications \nthat hold sensitive data, this could be disastrous.  \n5.4.2.3 Extraneous Files \nWhen we move a Web server from development into production, one of the tasks often missed \nin the process is that of cleaning up any files not directly related to running the site or application, or \nthat might be artifacts of the development or build process. \nIf we leave archives of the source code from which our applications are built, backup copies \nof our files, text files containing our notes or credentials, or any such related files, we may be handing", "chunk_id": "b4f66f12-a29e-4cbf-993f-9954fe062099", "chroma:document": "158 \n \nThese types of attacks are, for the most part, thwarted by the newer versions of the common \nbrowsers, such as Internet Explorer, Firefox, Safari, and Chrome. In many cases, however, new attack \nvectors are simply variations of old attacks. Additionally, there are innumerable vulnerable clients"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 314431f7-bbba-4d31-9ecd-f8d408d68902
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 157, "full_page_content": "158 \n \nThese types of attacks are, for the most part, thwarted by the newer versions of the common \nbrowsers, such as Internet Explorer, Firefox, Safari, and Chrome. In many cases, however, new attack \nvectors are simply variations of old attacks. Additionally, there are innumerable vulnerable clients \nrunning on outdated or unpatched software that are still vulnerable to attacks that are years old. \n5.4.2 Server-Side Attacks \nOn the server side of the Web transaction, a number of vulnerabilities may cause us problems \nas well. Such threats and vulnerabilities can vary widely depending on our operating system, Web \nserver software, various software versions, scripting languages, and many other factors.  \n5.4.2.1 Lack of Input Validation \nSQL injection gives us a strong example of what might happen if we do not properly validate \nthe input of our Web applications. Structured Query Language (SQL) is the language we use to \ncommunicate with many of the common databases on the market today. In the case of databases \nconnected to Web applications, entering specially crafted data into the Web forms that interact with \nthem can sometimes produce results not anticipated by the application developers.  \n5.4.2.2 Improper or Inadequate Permissions \nInadequate permissions can often cause us problems with Web applications, and Internet-\nfacing applications of most any kind. Particularly with Web applications and pages, there are often \nsensitive files and directories that will cause security issues if they are exposed to general users. One \narea that might cause us trouble is the exposure of configuration files.  \nFor example, in many Web applications that make use of a database (that is a vast majority \nof them), there are configuration files that hold the credentials the application uses to access the \ndatabase. If these files and the directories that hold them are not properly secured, an attacker may \nsimply read our credentials from the file and access the database as he or she pleases. For applications \nthat hold sensitive data, this could be disastrous.  \n5.4.2.3 Extraneous Files \nWhen we move a Web server from development into production, one of the tasks often missed \nin the process is that of cleaning up any files not directly related to running the site or application, or \nthat might be artifacts of the development or build process. \nIf we leave archives of the source code from which our applications are built, backup copies \nof our files, text files containing our notes or credentials, or any such related files, we may be handing", "chunk_id": "ce2aca55-ef33-4e7e-8e91-b50257fba24a", "chroma:document": "running on outdated or unpatched software that are still vulnerable to attacks that are years old. \n5.4.2 Server-Side Attacks \nOn the server side of the Web transaction, a number of vulnerabilities may cause us problems \nas well. Such threats and vulnerabilities can vary widely depending on our operating system, Web"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: f9070f2c-e87b-418b-84c2-e77d71fdda1d
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 157, "full_page_content": "158 \n \nThese types of attacks are, for the most part, thwarted by the newer versions of the common \nbrowsers, such as Internet Explorer, Firefox, Safari, and Chrome. In many cases, however, new attack \nvectors are simply variations of old attacks. Additionally, there are innumerable vulnerable clients \nrunning on outdated or unpatched software that are still vulnerable to attacks that are years old. \n5.4.2 Server-Side Attacks \nOn the server side of the Web transaction, a number of vulnerabilities may cause us problems \nas well. Such threats and vulnerabilities can vary widely depending on our operating system, Web \nserver software, various software versions, scripting languages, and many other factors.  \n5.4.2.1 Lack of Input Validation \nSQL injection gives us a strong example of what might happen if we do not properly validate \nthe input of our Web applications. Structured Query Language (SQL) is the language we use to \ncommunicate with many of the common databases on the market today. In the case of databases \nconnected to Web applications, entering specially crafted data into the Web forms that interact with \nthem can sometimes produce results not anticipated by the application developers.  \n5.4.2.2 Improper or Inadequate Permissions \nInadequate permissions can often cause us problems with Web applications, and Internet-\nfacing applications of most any kind. Particularly with Web applications and pages, there are often \nsensitive files and directories that will cause security issues if they are exposed to general users. One \narea that might cause us trouble is the exposure of configuration files.  \nFor example, in many Web applications that make use of a database (that is a vast majority \nof them), there are configuration files that hold the credentials the application uses to access the \ndatabase. If these files and the directories that hold them are not properly secured, an attacker may \nsimply read our credentials from the file and access the database as he or she pleases. For applications \nthat hold sensitive data, this could be disastrous.  \n5.4.2.3 Extraneous Files \nWhen we move a Web server from development into production, one of the tasks often missed \nin the process is that of cleaning up any files not directly related to running the site or application, or \nthat might be artifacts of the development or build process. \nIf we leave archives of the source code from which our applications are built, backup copies \nof our files, text files containing our notes or credentials, or any such related files, we may be handing", "chunk_id": "b063ec17-f807-4b32-b7a0-6bafd77f52d2", "chroma:document": "server software, various software versions, scripting languages, and many other factors.  \n5.4.2.1 Lack of Input Validation \nSQL injection gives us a strong example of what might happen if we do not properly validate \nthe input of our Web applications. Structured Query Language (SQL) is the language we use to"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 27549dfc-e918-4413-aaf1-cdc14f147107
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 157, "full_page_content": "158 \n \nThese types of attacks are, for the most part, thwarted by the newer versions of the common \nbrowsers, such as Internet Explorer, Firefox, Safari, and Chrome. In many cases, however, new attack \nvectors are simply variations of old attacks. Additionally, there are innumerable vulnerable clients \nrunning on outdated or unpatched software that are still vulnerable to attacks that are years old. \n5.4.2 Server-Side Attacks \nOn the server side of the Web transaction, a number of vulnerabilities may cause us problems \nas well. Such threats and vulnerabilities can vary widely depending on our operating system, Web \nserver software, various software versions, scripting languages, and many other factors.  \n5.4.2.1 Lack of Input Validation \nSQL injection gives us a strong example of what might happen if we do not properly validate \nthe input of our Web applications. Structured Query Language (SQL) is the language we use to \ncommunicate with many of the common databases on the market today. In the case of databases \nconnected to Web applications, entering specially crafted data into the Web forms that interact with \nthem can sometimes produce results not anticipated by the application developers.  \n5.4.2.2 Improper or Inadequate Permissions \nInadequate permissions can often cause us problems with Web applications, and Internet-\nfacing applications of most any kind. Particularly with Web applications and pages, there are often \nsensitive files and directories that will cause security issues if they are exposed to general users. One \narea that might cause us trouble is the exposure of configuration files.  \nFor example, in many Web applications that make use of a database (that is a vast majority \nof them), there are configuration files that hold the credentials the application uses to access the \ndatabase. If these files and the directories that hold them are not properly secured, an attacker may \nsimply read our credentials from the file and access the database as he or she pleases. For applications \nthat hold sensitive data, this could be disastrous.  \n5.4.2.3 Extraneous Files \nWhen we move a Web server from development into production, one of the tasks often missed \nin the process is that of cleaning up any files not directly related to running the site or application, or \nthat might be artifacts of the development or build process. \nIf we leave archives of the source code from which our applications are built, backup copies \nof our files, text files containing our notes or credentials, or any such related files, we may be handing", "chunk_id": "c149c14a-d89d-4b63-b241-fbbe2b27dccd", "chroma:document": "communicate with many of the common databases on the market today. In the case of databases \nconnected to Web applications, entering specially crafted data into the Web forms that interact with \nthem can sometimes produce results not anticipated by the application developers.  \n5.4.2.2 Improper or Inadequate Permissions"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 1ebbcdcb-e653-4584-bf3a-4286128eb50d
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 157, "full_page_content": "158 \n \nThese types of attacks are, for the most part, thwarted by the newer versions of the common \nbrowsers, such as Internet Explorer, Firefox, Safari, and Chrome. In many cases, however, new attack \nvectors are simply variations of old attacks. Additionally, there are innumerable vulnerable clients \nrunning on outdated or unpatched software that are still vulnerable to attacks that are years old. \n5.4.2 Server-Side Attacks \nOn the server side of the Web transaction, a number of vulnerabilities may cause us problems \nas well. Such threats and vulnerabilities can vary widely depending on our operating system, Web \nserver software, various software versions, scripting languages, and many other factors.  \n5.4.2.1 Lack of Input Validation \nSQL injection gives us a strong example of what might happen if we do not properly validate \nthe input of our Web applications. Structured Query Language (SQL) is the language we use to \ncommunicate with many of the common databases on the market today. In the case of databases \nconnected to Web applications, entering specially crafted data into the Web forms that interact with \nthem can sometimes produce results not anticipated by the application developers.  \n5.4.2.2 Improper or Inadequate Permissions \nInadequate permissions can often cause us problems with Web applications, and Internet-\nfacing applications of most any kind. Particularly with Web applications and pages, there are often \nsensitive files and directories that will cause security issues if they are exposed to general users. One \narea that might cause us trouble is the exposure of configuration files.  \nFor example, in many Web applications that make use of a database (that is a vast majority \nof them), there are configuration files that hold the credentials the application uses to access the \ndatabase. If these files and the directories that hold them are not properly secured, an attacker may \nsimply read our credentials from the file and access the database as he or she pleases. For applications \nthat hold sensitive data, this could be disastrous.  \n5.4.2.3 Extraneous Files \nWhen we move a Web server from development into production, one of the tasks often missed \nin the process is that of cleaning up any files not directly related to running the site or application, or \nthat might be artifacts of the development or build process. \nIf we leave archives of the source code from which our applications are built, backup copies \nof our files, text files containing our notes or credentials, or any such related files, we may be handing", "chunk_id": "a7c471ff-7859-4a5f-b162-a0ddc621ecbf", "chroma:document": "Inadequate permissions can often cause us problems with Web applications, and Internet-\nfacing applications of most any kind. Particularly with Web applications and pages, there are often \nsensitive files and directories that will cause security issues if they are exposed to general users. One \narea that might cause us trouble is the exposure of configuration files."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: b2ec68c9-01cc-4654-87e3-a2325d7b09c6
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 157, "full_page_content": "158 \n \nThese types of attacks are, for the most part, thwarted by the newer versions of the common \nbrowsers, such as Internet Explorer, Firefox, Safari, and Chrome. In many cases, however, new attack \nvectors are simply variations of old attacks. Additionally, there are innumerable vulnerable clients \nrunning on outdated or unpatched software that are still vulnerable to attacks that are years old. \n5.4.2 Server-Side Attacks \nOn the server side of the Web transaction, a number of vulnerabilities may cause us problems \nas well. Such threats and vulnerabilities can vary widely depending on our operating system, Web \nserver software, various software versions, scripting languages, and many other factors.  \n5.4.2.1 Lack of Input Validation \nSQL injection gives us a strong example of what might happen if we do not properly validate \nthe input of our Web applications. Structured Query Language (SQL) is the language we use to \ncommunicate with many of the common databases on the market today. In the case of databases \nconnected to Web applications, entering specially crafted data into the Web forms that interact with \nthem can sometimes produce results not anticipated by the application developers.  \n5.4.2.2 Improper or Inadequate Permissions \nInadequate permissions can often cause us problems with Web applications, and Internet-\nfacing applications of most any kind. Particularly with Web applications and pages, there are often \nsensitive files and directories that will cause security issues if they are exposed to general users. One \narea that might cause us trouble is the exposure of configuration files.  \nFor example, in many Web applications that make use of a database (that is a vast majority \nof them), there are configuration files that hold the credentials the application uses to access the \ndatabase. If these files and the directories that hold them are not properly secured, an attacker may \nsimply read our credentials from the file and access the database as he or she pleases. For applications \nthat hold sensitive data, this could be disastrous.  \n5.4.2.3 Extraneous Files \nWhen we move a Web server from development into production, one of the tasks often missed \nin the process is that of cleaning up any files not directly related to running the site or application, or \nthat might be artifacts of the development or build process. \nIf we leave archives of the source code from which our applications are built, backup copies \nof our files, text files containing our notes or credentials, or any such related files, we may be handing", "chunk_id": "0eabe0e5-0ec1-4eaa-9737-3526d5a75a5e", "chroma:document": "For example, in many Web applications that make use of a database (that is a vast majority \nof them), there are configuration files that hold the credentials the application uses to access the \ndatabase. If these files and the directories that hold them are not properly secured, an attacker may"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: d546f03c-327c-4d98-bc7d-c2018f194f01
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 157, "full_page_content": "158 \n \nThese types of attacks are, for the most part, thwarted by the newer versions of the common \nbrowsers, such as Internet Explorer, Firefox, Safari, and Chrome. In many cases, however, new attack \nvectors are simply variations of old attacks. Additionally, there are innumerable vulnerable clients \nrunning on outdated or unpatched software that are still vulnerable to attacks that are years old. \n5.4.2 Server-Side Attacks \nOn the server side of the Web transaction, a number of vulnerabilities may cause us problems \nas well. Such threats and vulnerabilities can vary widely depending on our operating system, Web \nserver software, various software versions, scripting languages, and many other factors.  \n5.4.2.1 Lack of Input Validation \nSQL injection gives us a strong example of what might happen if we do not properly validate \nthe input of our Web applications. Structured Query Language (SQL) is the language we use to \ncommunicate with many of the common databases on the market today. In the case of databases \nconnected to Web applications, entering specially crafted data into the Web forms that interact with \nthem can sometimes produce results not anticipated by the application developers.  \n5.4.2.2 Improper or Inadequate Permissions \nInadequate permissions can often cause us problems with Web applications, and Internet-\nfacing applications of most any kind. Particularly with Web applications and pages, there are often \nsensitive files and directories that will cause security issues if they are exposed to general users. One \narea that might cause us trouble is the exposure of configuration files.  \nFor example, in many Web applications that make use of a database (that is a vast majority \nof them), there are configuration files that hold the credentials the application uses to access the \ndatabase. If these files and the directories that hold them are not properly secured, an attacker may \nsimply read our credentials from the file and access the database as he or she pleases. For applications \nthat hold sensitive data, this could be disastrous.  \n5.4.2.3 Extraneous Files \nWhen we move a Web server from development into production, one of the tasks often missed \nin the process is that of cleaning up any files not directly related to running the site or application, or \nthat might be artifacts of the development or build process. \nIf we leave archives of the source code from which our applications are built, backup copies \nof our files, text files containing our notes or credentials, or any such related files, we may be handing", "chunk_id": "fb608734-842a-48a9-80ba-01ac301e578a", "chroma:document": "simply read our credentials from the file and access the database as he or she pleases. For applications \nthat hold sensitive data, this could be disastrous.  \n5.4.2.3 Extraneous Files \nWhen we move a Web server from development into production, one of the tasks often missed"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 4b1dceaf-50a2-444e-93d3-a96c74dd330c
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 157, "full_page_content": "158 \n \nThese types of attacks are, for the most part, thwarted by the newer versions of the common \nbrowsers, such as Internet Explorer, Firefox, Safari, and Chrome. In many cases, however, new attack \nvectors are simply variations of old attacks. Additionally, there are innumerable vulnerable clients \nrunning on outdated or unpatched software that are still vulnerable to attacks that are years old. \n5.4.2 Server-Side Attacks \nOn the server side of the Web transaction, a number of vulnerabilities may cause us problems \nas well. Such threats and vulnerabilities can vary widely depending on our operating system, Web \nserver software, various software versions, scripting languages, and many other factors.  \n5.4.2.1 Lack of Input Validation \nSQL injection gives us a strong example of what might happen if we do not properly validate \nthe input of our Web applications. Structured Query Language (SQL) is the language we use to \ncommunicate with many of the common databases on the market today. In the case of databases \nconnected to Web applications, entering specially crafted data into the Web forms that interact with \nthem can sometimes produce results not anticipated by the application developers.  \n5.4.2.2 Improper or Inadequate Permissions \nInadequate permissions can often cause us problems with Web applications, and Internet-\nfacing applications of most any kind. Particularly with Web applications and pages, there are often \nsensitive files and directories that will cause security issues if they are exposed to general users. One \narea that might cause us trouble is the exposure of configuration files.  \nFor example, in many Web applications that make use of a database (that is a vast majority \nof them), there are configuration files that hold the credentials the application uses to access the \ndatabase. If these files and the directories that hold them are not properly secured, an attacker may \nsimply read our credentials from the file and access the database as he or she pleases. For applications \nthat hold sensitive data, this could be disastrous.  \n5.4.2.3 Extraneous Files \nWhen we move a Web server from development into production, one of the tasks often missed \nin the process is that of cleaning up any files not directly related to running the site or application, or \nthat might be artifacts of the development or build process. \nIf we leave archives of the source code from which our applications are built, backup copies \nof our files, text files containing our notes or credentials, or any such related files, we may be handing", "chunk_id": "b2c82d66-63fd-410b-a10b-b9fbeb998624", "chroma:document": "in the process is that of cleaning up any files not directly related to running the site or application, or \nthat might be artifacts of the development or build process. \nIf we leave archives of the source code from which our applications are built, backup copies \nof our files, text files containing our notes or credentials, or any such related files, we may be handing"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 685582ac-ca2a-407a-98a7-bc8afb00f76c
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 158, "full_page_content": "159 \n \nan attacker exactly the materials he or she needs in order to compromise our system. One of the final \nsteps when we are rolling out such a server should be to make sure all such files are cleaned up, or \nmoved elsewhere if they are still needed.  \n5.5 Database security \nIn some cases, applications may hold very sensitive data, such as tax returns, medical data, or \nlegal records; or they may contain only the contents of a discussion forum on knitting. In either case, \nthe data such applications hold is important to the owners of the application and they would be \ninconvenienced, at the very least, if it were damaged or manipulated in an unauthorized manner. A \nnumber of issues can cause trouble in ensuring the security of our databases. The canonical list \nincludes the following:  \n\u2022 Unauthenticated flaws in network protocols  \n\u2022 Authenticated flaws in network protocols \n\u2022 Flaws in authentication protocols \n\u2022 Unauthenticated access to functionality \n \nFig 2 Categories of Database Security Issues \n \n\u2022 Arbitrary code execution in intrinsic SQL elements \n\u2022 Arbitrary code execution in securable SQL elements \n\u2022 Privilege escalation via SQL injection \n\u2022 Local privilege escalation issues", "chunk_id": "9d944b66-6068-4f7a-8599-7b346f06a1f6", "chroma:document": "159 \n \nan attacker exactly the materials he or she needs in order to compromise our system. One of the final \nsteps when we are rolling out such a server should be to make sure all such files are cleaned up, or \nmoved elsewhere if they are still needed.  \n5.5 Database security \nIn some cases, applications may hold very sensitive data, such as tax returns, medical data, or"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 0887d6d8-31b0-4c12-a948-72be9b2ea9c2
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 158, "full_page_content": "159 \n \nan attacker exactly the materials he or she needs in order to compromise our system. One of the final \nsteps when we are rolling out such a server should be to make sure all such files are cleaned up, or \nmoved elsewhere if they are still needed.  \n5.5 Database security \nIn some cases, applications may hold very sensitive data, such as tax returns, medical data, or \nlegal records; or they may contain only the contents of a discussion forum on knitting. In either case, \nthe data such applications hold is important to the owners of the application and they would be \ninconvenienced, at the very least, if it were damaged or manipulated in an unauthorized manner. A \nnumber of issues can cause trouble in ensuring the security of our databases. The canonical list \nincludes the following:  \n\u2022 Unauthenticated flaws in network protocols  \n\u2022 Authenticated flaws in network protocols \n\u2022 Flaws in authentication protocols \n\u2022 Unauthenticated access to functionality \n \nFig 2 Categories of Database Security Issues \n \n\u2022 Arbitrary code execution in intrinsic SQL elements \n\u2022 Arbitrary code execution in securable SQL elements \n\u2022 Privilege escalation via SQL injection \n\u2022 Local privilege escalation issues", "chunk_id": "fbe2c75e-f3a9-4986-8cbb-b8d500cce522", "chroma:document": "legal records; or they may contain only the contents of a discussion forum on knitting. In either case, \nthe data such applications hold is important to the owners of the application and they would be \ninconvenienced, at the very least, if it were damaged or manipulated in an unauthorized manner. A"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: e3d1323a-bab4-4928-b340-38f0c90f912a
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 158, "full_page_content": "159 \n \nan attacker exactly the materials he or she needs in order to compromise our system. One of the final \nsteps when we are rolling out such a server should be to make sure all such files are cleaned up, or \nmoved elsewhere if they are still needed.  \n5.5 Database security \nIn some cases, applications may hold very sensitive data, such as tax returns, medical data, or \nlegal records; or they may contain only the contents of a discussion forum on knitting. In either case, \nthe data such applications hold is important to the owners of the application and they would be \ninconvenienced, at the very least, if it were damaged or manipulated in an unauthorized manner. A \nnumber of issues can cause trouble in ensuring the security of our databases. The canonical list \nincludes the following:  \n\u2022 Unauthenticated flaws in network protocols  \n\u2022 Authenticated flaws in network protocols \n\u2022 Flaws in authentication protocols \n\u2022 Unauthenticated access to functionality \n \nFig 2 Categories of Database Security Issues \n \n\u2022 Arbitrary code execution in intrinsic SQL elements \n\u2022 Arbitrary code execution in securable SQL elements \n\u2022 Privilege escalation via SQL injection \n\u2022 Local privilege escalation issues", "chunk_id": "775a4d7d-53cf-434b-b205-0ff3096acb99", "chroma:document": "number of issues can cause trouble in ensuring the security of our databases. The canonical list \nincludes the following:  \n\u2022 Unauthenticated flaws in network protocols  \n\u2022 Authenticated flaws in network protocols \n\u2022 Flaws in authentication protocols \n\u2022 Unauthenticated access to functionality \n \nFig 2 Categories of Database Security Issues"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: c60c560e-5f1b-4859-abef-fce1275e8ce9
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 158, "full_page_content": "159 \n \nan attacker exactly the materials he or she needs in order to compromise our system. One of the final \nsteps when we are rolling out such a server should be to make sure all such files are cleaned up, or \nmoved elsewhere if they are still needed.  \n5.5 Database security \nIn some cases, applications may hold very sensitive data, such as tax returns, medical data, or \nlegal records; or they may contain only the contents of a discussion forum on knitting. In either case, \nthe data such applications hold is important to the owners of the application and they would be \ninconvenienced, at the very least, if it were damaged or manipulated in an unauthorized manner. A \nnumber of issues can cause trouble in ensuring the security of our databases. The canonical list \nincludes the following:  \n\u2022 Unauthenticated flaws in network protocols  \n\u2022 Authenticated flaws in network protocols \n\u2022 Flaws in authentication protocols \n\u2022 Unauthenticated access to functionality \n \nFig 2 Categories of Database Security Issues \n \n\u2022 Arbitrary code execution in intrinsic SQL elements \n\u2022 Arbitrary code execution in securable SQL elements \n\u2022 Privilege escalation via SQL injection \n\u2022 Local privilege escalation issues", "chunk_id": "ba5d1a26-d625-4023-8d5b-559a7a5f3d36", "chroma:document": "\u2022 Arbitrary code execution in intrinsic SQL elements \n\u2022 Arbitrary code execution in securable SQL elements \n\u2022 Privilege escalation via SQL injection \n\u2022 Local privilege escalation issues"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: c4bf872d-9be2-4a98-8b68-3365cf409d15
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 159, "full_page_content": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development \nissues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol \nproblems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple \nqueries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user \nor process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the \ndefault SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure \ncoding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution \nIn the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the \nmemory space used by the database or the operating system, and compromise either or both of them.", "chunk_id": "98fd1dab-28ad-4aa5-b651-aa4a1f05e343", "chroma:document": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 7f95a112-05b8-499a-84ae-0b44d6127c82
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 159, "full_page_content": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development \nissues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol \nproblems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple \nqueries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user \nor process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the \ndefault SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure \ncoding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution \nIn the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the \nmemory space used by the database or the operating system, and compromise either or both of them.", "chunk_id": "c4a7c7cc-1c4a-4ca1-87b3-07c84dfce1cc", "chroma:document": "issues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: a592c396-c7e6-4327-8db6-84f411ff3daa
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 159, "full_page_content": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development \nissues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol \nproblems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple \nqueries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user \nor process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the \ndefault SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure \ncoding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution \nIn the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the \nmemory space used by the database or the operating system, and compromise either or both of them.", "chunk_id": "cc12e820-b073-4ec6-b3d6-d2ff3ee31810", "chroma:document": "problems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 58e58ad3-e758-47ca-aec2-8aab0a2e94c3
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 159, "full_page_content": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development \nissues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol \nproblems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple \nqueries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user \nor process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the \ndefault SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure \ncoding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution \nIn the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the \nmemory space used by the database or the operating system, and compromise either or both of them.", "chunk_id": "e5ff853a-fad7-4c37-8fa9-6b2404635dc8", "chroma:document": "queries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: a90bdf8e-5aab-446b-8911-ffbace249a1c
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 159, "full_page_content": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development \nissues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol \nproblems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple \nqueries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user \nor process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the \ndefault SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure \ncoding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution \nIn the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the \nmemory space used by the database or the operating system, and compromise either or both of them.", "chunk_id": "68c28d9d-db91-4a52-aa4a-5e578bafcc10", "chroma:document": "or process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: d83b8f89-84a7-4fc8-9b67-21211a0315a9
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 159, "full_page_content": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development \nissues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol \nproblems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple \nqueries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user \nor process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the \ndefault SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure \ncoding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution \nIn the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the \nmemory space used by the database or the operating system, and compromise either or both of them.", "chunk_id": "e56f1316-103b-4eb2-b7df-1340aefdbe80", "chroma:document": "default SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: c49dc390-4a2a-4949-bcc9-1b6bcb9b2804
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 159, "full_page_content": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development \nissues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol \nproblems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple \nqueries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user \nor process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the \ndefault SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure \ncoding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution \nIn the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the \nmemory space used by the database or the operating system, and compromise either or both of them.", "chunk_id": "00f30586-7e00-4976-8d8f-31dba46c1af8", "chroma:document": "coding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 6480ac47-0a3f-49df-9b34-0f563a599d5e
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 159, "full_page_content": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development \nissues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol \nproblems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple \nqueries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user \nor process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the \ndefault SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure \ncoding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution \nIn the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the \nmemory space used by the database or the operating system, and compromise either or both of them.", "chunk_id": "f5f7ca05-b626-41c9-a78d-65ac2a684b48", "chroma:document": "In the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 17ca983a-5bdb-4bcd-88b5-05abf4bf39a6
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 159, "full_page_content": "160 \n \n5.5.1 Protocol Issues  \n \nWe might find a number of issues in the protocols in use by any given database. In either case, there \nis often a steady stream of vulnerabilities for most any major database product and version we might \ncare to examine. Such vulnerabilities often involve some of the more common software development \nissues. Defending against presently unknown network protocol issues often revolves around limiting \naccess to our databases, either in the sense of actually limiting access to who is able to connect to the \ndatabase over the network, using some of the methods or, in the case of authenticated protocol \nproblems, by limiting the privileges and accounts make available for the database itself, following \nthe principle of least privilege. \n \n5.5.2 Unauthenticated Access  \n \nWhen we give a user or process the opportunity to interact with our database without supplying a set \nof credentials, we create the possibility for security issues. Such issues may be related to simple \nqueries to the database through a Web interface, in which we might accidentally expose information \ncontained in the database; or we might expose information on the database itself, such as a version \nnumber, giving an attacker additional material with which to compromise our application. If the user \nor process is forced to send us a set of credentials to begin a transaction, we can monitor, or place \nlimits on, what the user or process is allowed to do, based on those credentials.  \n \nGenerally, these are concentrated on SQL, as it is the most common database language in use. In the \ndefault SQL language, a number of builtin elements are possible security risks, some of which we \ncan control access to and some of which we cannot. In these language elements, we may find a \nnumber of issues related to bugs in the software we are using, or issues spawned by not using secure \ncoding practices, that might allow us to execute arbitrary code within the application. For example, \na flaw allowing us to conduct a buffer overflow might enable us to insert attack code into the memory \nspace used by the database or the operating system, and compromise either or both of them.  \n \n5.5.3 Arbitrary Code Execution \nIn the default SQL language, a number of builtin elements are possible security risks, ome of which \nwe can control access to and some of which we cannot.For example, a flaw allowing us to conduct a \nbuffer overflow, as we discussed earlier in this chapter, might enable us to insert attack code into the \nmemory space used by the database or the operating system, and compromise either or both of them.", "chunk_id": "21246d80-6fd8-4e96-9db4-ea7e50e72985", "chroma:document": "memory space used by the database or the operating system, and compromise either or both of them."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: d46d2edb-c6b4-4b3e-9cdd-5efe7734292e
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 160, "full_page_content": "161 \n \nOur best defenses against such attacks are twofold. From the consumer side, we should stay current \non the version and patch levels for our software. From the vendor side, we should mandate secure \ncoding practices, in all cases, in order to eliminate the vulnerabilities in the first place, as well as \nconducting internal reviews to ensure that such practices are actually being followed. \n \n5.5.4 Privilege Escalation \n  \n Privilege escalation is a category of attack in which we make use of any of a number of methods to \nincrease the level of access above what we are authorized to have, or have managed to gain on the \nsystem or application through attack. Privilege escalation is aimed at gaining administrative access \nto the software in order to carry out other attacks without needing to worry about not having the \naccess required. SQL injection can be used to gain information from the database in an unauthorized \nmanner, modify data contained in the database, and perform many other similar activities. SQL \ninjection can also be used to gain or escalate privileges in the database.  \n \n5.6 Application security tools \n \n There are number of tools in an attempt to assess and improve the security of our applications.  \n5.6.1 Sniffers \n \n     Sniffers can be of great use in a variety of security situations. We can use them at a very high level \nto examine all the traffic traveling over the portion of the network to which we are attached, \npresuming we can get our sniffer placed properly to see the traffic in question. Such tools can be used \nvery specifically in order to watch the network traffic being exchanged with a particular application \nor protocol. In Figure 3, we are using Wireshark to examine Hypertext Transfer Protocol (HTTP) \ntraffic specifically.", "chunk_id": "e20fb0fc-8c00-4fff-800c-e2518863d940", "chroma:document": "161 \n \nOur best defenses against such attacks are twofold. From the consumer side, we should stay current \non the version and patch levels for our software. From the vendor side, we should mandate secure \ncoding practices, in all cases, in order to eliminate the vulnerabilities in the first place, as well as"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 0696488d-59ca-4183-b1f3-1aed00559c5f
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 160, "full_page_content": "161 \n \nOur best defenses against such attacks are twofold. From the consumer side, we should stay current \non the version and patch levels for our software. From the vendor side, we should mandate secure \ncoding practices, in all cases, in order to eliminate the vulnerabilities in the first place, as well as \nconducting internal reviews to ensure that such practices are actually being followed. \n \n5.5.4 Privilege Escalation \n  \n Privilege escalation is a category of attack in which we make use of any of a number of methods to \nincrease the level of access above what we are authorized to have, or have managed to gain on the \nsystem or application through attack. Privilege escalation is aimed at gaining administrative access \nto the software in order to carry out other attacks without needing to worry about not having the \naccess required. SQL injection can be used to gain information from the database in an unauthorized \nmanner, modify data contained in the database, and perform many other similar activities. SQL \ninjection can also be used to gain or escalate privileges in the database.  \n \n5.6 Application security tools \n \n There are number of tools in an attempt to assess and improve the security of our applications.  \n5.6.1 Sniffers \n \n     Sniffers can be of great use in a variety of security situations. We can use them at a very high level \nto examine all the traffic traveling over the portion of the network to which we are attached, \npresuming we can get our sniffer placed properly to see the traffic in question. Such tools can be used \nvery specifically in order to watch the network traffic being exchanged with a particular application \nor protocol. In Figure 3, we are using Wireshark to examine Hypertext Transfer Protocol (HTTP) \ntraffic specifically.", "chunk_id": "825b7a66-593f-4165-a0cf-9ba7de92debf", "chroma:document": "conducting internal reviews to ensure that such practices are actually being followed. \n \n5.5.4 Privilege Escalation \n  \n Privilege escalation is a category of attack in which we make use of any of a number of methods to \nincrease the level of access above what we are authorized to have, or have managed to gain on the"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 86a7ec0a-a539-4acd-b3f1-f6c1b012ce35
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 160, "full_page_content": "161 \n \nOur best defenses against such attacks are twofold. From the consumer side, we should stay current \non the version and patch levels for our software. From the vendor side, we should mandate secure \ncoding practices, in all cases, in order to eliminate the vulnerabilities in the first place, as well as \nconducting internal reviews to ensure that such practices are actually being followed. \n \n5.5.4 Privilege Escalation \n  \n Privilege escalation is a category of attack in which we make use of any of a number of methods to \nincrease the level of access above what we are authorized to have, or have managed to gain on the \nsystem or application through attack. Privilege escalation is aimed at gaining administrative access \nto the software in order to carry out other attacks without needing to worry about not having the \naccess required. SQL injection can be used to gain information from the database in an unauthorized \nmanner, modify data contained in the database, and perform many other similar activities. SQL \ninjection can also be used to gain or escalate privileges in the database.  \n \n5.6 Application security tools \n \n There are number of tools in an attempt to assess and improve the security of our applications.  \n5.6.1 Sniffers \n \n     Sniffers can be of great use in a variety of security situations. We can use them at a very high level \nto examine all the traffic traveling over the portion of the network to which we are attached, \npresuming we can get our sniffer placed properly to see the traffic in question. Such tools can be used \nvery specifically in order to watch the network traffic being exchanged with a particular application \nor protocol. In Figure 3, we are using Wireshark to examine Hypertext Transfer Protocol (HTTP) \ntraffic specifically.", "chunk_id": "0b96d2be-0a1b-4d45-9ac2-79946d589ea8", "chroma:document": "system or application through attack. Privilege escalation is aimed at gaining administrative access \nto the software in order to carry out other attacks without needing to worry about not having the \naccess required. SQL injection can be used to gain information from the database in an unauthorized"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 3d3723cc-a918-4bef-859e-8402e9c5f222
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 160, "full_page_content": "161 \n \nOur best defenses against such attacks are twofold. From the consumer side, we should stay current \non the version and patch levels for our software. From the vendor side, we should mandate secure \ncoding practices, in all cases, in order to eliminate the vulnerabilities in the first place, as well as \nconducting internal reviews to ensure that such practices are actually being followed. \n \n5.5.4 Privilege Escalation \n  \n Privilege escalation is a category of attack in which we make use of any of a number of methods to \nincrease the level of access above what we are authorized to have, or have managed to gain on the \nsystem or application through attack. Privilege escalation is aimed at gaining administrative access \nto the software in order to carry out other attacks without needing to worry about not having the \naccess required. SQL injection can be used to gain information from the database in an unauthorized \nmanner, modify data contained in the database, and perform many other similar activities. SQL \ninjection can also be used to gain or escalate privileges in the database.  \n \n5.6 Application security tools \n \n There are number of tools in an attempt to assess and improve the security of our applications.  \n5.6.1 Sniffers \n \n     Sniffers can be of great use in a variety of security situations. We can use them at a very high level \nto examine all the traffic traveling over the portion of the network to which we are attached, \npresuming we can get our sniffer placed properly to see the traffic in question. Such tools can be used \nvery specifically in order to watch the network traffic being exchanged with a particular application \nor protocol. In Figure 3, we are using Wireshark to examine Hypertext Transfer Protocol (HTTP) \ntraffic specifically.", "chunk_id": "06c3e276-065a-43fc-a4a7-65fb7fb1919a", "chroma:document": "manner, modify data contained in the database, and perform many other similar activities. SQL \ninjection can also be used to gain or escalate privileges in the database.  \n \n5.6 Application security tools \n \n There are number of tools in an attempt to assess and improve the security of our applications.  \n5.6.1 Sniffers"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 6f8015e4-7397-45b9-a73f-b7c2f93ac15b
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 160, "full_page_content": "161 \n \nOur best defenses against such attacks are twofold. From the consumer side, we should stay current \non the version and patch levels for our software. From the vendor side, we should mandate secure \ncoding practices, in all cases, in order to eliminate the vulnerabilities in the first place, as well as \nconducting internal reviews to ensure that such practices are actually being followed. \n \n5.5.4 Privilege Escalation \n  \n Privilege escalation is a category of attack in which we make use of any of a number of methods to \nincrease the level of access above what we are authorized to have, or have managed to gain on the \nsystem or application through attack. Privilege escalation is aimed at gaining administrative access \nto the software in order to carry out other attacks without needing to worry about not having the \naccess required. SQL injection can be used to gain information from the database in an unauthorized \nmanner, modify data contained in the database, and perform many other similar activities. SQL \ninjection can also be used to gain or escalate privileges in the database.  \n \n5.6 Application security tools \n \n There are number of tools in an attempt to assess and improve the security of our applications.  \n5.6.1 Sniffers \n \n     Sniffers can be of great use in a variety of security situations. We can use them at a very high level \nto examine all the traffic traveling over the portion of the network to which we are attached, \npresuming we can get our sniffer placed properly to see the traffic in question. Such tools can be used \nvery specifically in order to watch the network traffic being exchanged with a particular application \nor protocol. In Figure 3, we are using Wireshark to examine Hypertext Transfer Protocol (HTTP) \ntraffic specifically.", "chunk_id": "fd0718c2-d706-4c02-bf56-e9f73ed7b897", "chroma:document": "5.6.1 Sniffers \n \n     Sniffers can be of great use in a variety of security situations. We can use them at a very high level \nto examine all the traffic traveling over the portion of the network to which we are attached, \npresuming we can get our sniffer placed properly to see the traffic in question. Such tools can be used"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 3bd460c3-2408-48e9-926e-d4ab956a60e0
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 160, "full_page_content": "161 \n \nOur best defenses against such attacks are twofold. From the consumer side, we should stay current \non the version and patch levels for our software. From the vendor side, we should mandate secure \ncoding practices, in all cases, in order to eliminate the vulnerabilities in the first place, as well as \nconducting internal reviews to ensure that such practices are actually being followed. \n \n5.5.4 Privilege Escalation \n  \n Privilege escalation is a category of attack in which we make use of any of a number of methods to \nincrease the level of access above what we are authorized to have, or have managed to gain on the \nsystem or application through attack. Privilege escalation is aimed at gaining administrative access \nto the software in order to carry out other attacks without needing to worry about not having the \naccess required. SQL injection can be used to gain information from the database in an unauthorized \nmanner, modify data contained in the database, and perform many other similar activities. SQL \ninjection can also be used to gain or escalate privileges in the database.  \n \n5.6 Application security tools \n \n There are number of tools in an attempt to assess and improve the security of our applications.  \n5.6.1 Sniffers \n \n     Sniffers can be of great use in a variety of security situations. We can use them at a very high level \nto examine all the traffic traveling over the portion of the network to which we are attached, \npresuming we can get our sniffer placed properly to see the traffic in question. Such tools can be used \nvery specifically in order to watch the network traffic being exchanged with a particular application \nor protocol. In Figure 3, we are using Wireshark to examine Hypertext Transfer Protocol (HTTP) \ntraffic specifically.", "chunk_id": "dd194021-984d-47a8-aa4b-54e3d3511f62", "chroma:document": "very specifically in order to watch the network traffic being exchanged with a particular application \nor protocol. In Figure 3, we are using Wireshark to examine Hypertext Transfer Protocol (HTTP) \ntraffic specifically."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 6f9c81c5-6e56-4020-8745-4e309362fc3a
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 161, "full_page_content": "162 \n \n \nFig 3 Wireshark Examining HTTP Traffic \nA good example of this is the Microsoft Network Monitor tool, which will enable us to not only sniff \nthe network traffic but also easily associate the traffic we are seeing with a particular application or \nprocess running on the system. This allows us to very specifically track information we see on the \nnetwork interface of the system back to a certain process, as shown in Figure 4", "chunk_id": "c1503185-f742-419b-8a2c-c11274a496a6", "chroma:document": "162 \n \n \nFig 3 Wireshark Examining HTTP Traffic \nA good example of this is the Microsoft Network Monitor tool, which will enable us to not only sniff \nthe network traffic but also easily associate the traffic we are seeing with a particular application or \nprocess running on the system. This allows us to very specifically track information we see on the"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: b91e9282-db14-479b-bcc7-3afcf5268989
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 161, "full_page_content": "162 \n \n \nFig 3 Wireshark Examining HTTP Traffic \nA good example of this is the Microsoft Network Monitor tool, which will enable us to not only sniff \nthe network traffic but also easily associate the traffic we are seeing with a particular application or \nprocess running on the system. This allows us to very specifically track information we see on the \nnetwork interface of the system back to a certain process, as shown in Figure 4", "chunk_id": "8016b3b6-0137-45a8-bc9e-8444e10e2444", "chroma:document": "network interface of the system back to a certain process, as shown in Figure 4"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 5fcc5ebb-6f1d-4ab5-b155-119fa0db9d03
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 162, "full_page_content": "163 \n \n \nFig 4 Microsoft Network Monitor Examining Traffic from an application \n \n5.6.2 Web Application Analysis Tools \n For purposes of analyzing Web pages or Web-based applications, a great number of tools exist, some \nof them commercial and some of them free. Most of these tools perform the same general set of tasks \nand will search for common flaws such as XSS or SQL injection flaws, as well as improperly set \npermissions, extraneous files, outdated software versions, and many more such items. \n \n5.6.2.1 Nikto and Wikto \n \n Nikto is a free and open source Web server analysis tool that will perform checks for many of the \ncommon vulnerabilities. Nikto will index all the files and directories it can see on the target Web \nserver, a process commonly referred to as spidering, and will then locate and report on any potential \nissues it finds. \nNikto is a command-line interface tool that runs on Linux. For those of us who are in a Windows-\ncentric environment, or prefer to use a graphical interface, SensePost has produced a Windows \nversion of Nikto called Wikto, as shown in Figure 5. Wikto is very similar in functionality to Nikto \nand provides us with a GUI.", "chunk_id": "b172ad7c-98bb-4963-b602-d5d1ddc6b051", "chroma:document": "163 \n \n \nFig 4 Microsoft Network Monitor Examining Traffic from an application \n \n5.6.2 Web Application Analysis Tools \n For purposes of analyzing Web pages or Web-based applications, a great number of tools exist, some \nof them commercial and some of them free. Most of these tools perform the same general set of tasks"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: e7c7659d-5b50-4135-9997-4b9c3075abc0
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 162, "full_page_content": "163 \n \n \nFig 4 Microsoft Network Monitor Examining Traffic from an application \n \n5.6.2 Web Application Analysis Tools \n For purposes of analyzing Web pages or Web-based applications, a great number of tools exist, some \nof them commercial and some of them free. Most of these tools perform the same general set of tasks \nand will search for common flaws such as XSS or SQL injection flaws, as well as improperly set \npermissions, extraneous files, outdated software versions, and many more such items. \n \n5.6.2.1 Nikto and Wikto \n \n Nikto is a free and open source Web server analysis tool that will perform checks for many of the \ncommon vulnerabilities. Nikto will index all the files and directories it can see on the target Web \nserver, a process commonly referred to as spidering, and will then locate and report on any potential \nissues it finds. \nNikto is a command-line interface tool that runs on Linux. For those of us who are in a Windows-\ncentric environment, or prefer to use a graphical interface, SensePost has produced a Windows \nversion of Nikto called Wikto, as shown in Figure 5. Wikto is very similar in functionality to Nikto \nand provides us with a GUI.", "chunk_id": "0ce65772-3557-4ee3-b0b0-5e97b9208b7b", "chroma:document": "and will search for common flaws such as XSS or SQL injection flaws, as well as improperly set \npermissions, extraneous files, outdated software versions, and many more such items. \n \n5.6.2.1 Nikto and Wikto \n \n Nikto is a free and open source Web server analysis tool that will perform checks for many of the"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 35c4dd24-fbf4-4c0a-8389-dc3f71664045
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 162, "full_page_content": "163 \n \n \nFig 4 Microsoft Network Monitor Examining Traffic from an application \n \n5.6.2 Web Application Analysis Tools \n For purposes of analyzing Web pages or Web-based applications, a great number of tools exist, some \nof them commercial and some of them free. Most of these tools perform the same general set of tasks \nand will search for common flaws such as XSS or SQL injection flaws, as well as improperly set \npermissions, extraneous files, outdated software versions, and many more such items. \n \n5.6.2.1 Nikto and Wikto \n \n Nikto is a free and open source Web server analysis tool that will perform checks for many of the \ncommon vulnerabilities. Nikto will index all the files and directories it can see on the target Web \nserver, a process commonly referred to as spidering, and will then locate and report on any potential \nissues it finds. \nNikto is a command-line interface tool that runs on Linux. For those of us who are in a Windows-\ncentric environment, or prefer to use a graphical interface, SensePost has produced a Windows \nversion of Nikto called Wikto, as shown in Figure 5. Wikto is very similar in functionality to Nikto \nand provides us with a GUI.", "chunk_id": "cdf0caff-2503-40ca-9902-698f0f1e5518", "chroma:document": "common vulnerabilities. Nikto will index all the files and directories it can see on the target Web \nserver, a process commonly referred to as spidering, and will then locate and report on any potential \nissues it finds. \nNikto is a command-line interface tool that runs on Linux. For those of us who are in a Windows-"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 7c60bf41-6bbb-4b5f-9df9-2165cc63f7db
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 162, "full_page_content": "163 \n \n \nFig 4 Microsoft Network Monitor Examining Traffic from an application \n \n5.6.2 Web Application Analysis Tools \n For purposes of analyzing Web pages or Web-based applications, a great number of tools exist, some \nof them commercial and some of them free. Most of these tools perform the same general set of tasks \nand will search for common flaws such as XSS or SQL injection flaws, as well as improperly set \npermissions, extraneous files, outdated software versions, and many more such items. \n \n5.6.2.1 Nikto and Wikto \n \n Nikto is a free and open source Web server analysis tool that will perform checks for many of the \ncommon vulnerabilities. Nikto will index all the files and directories it can see on the target Web \nserver, a process commonly referred to as spidering, and will then locate and report on any potential \nissues it finds. \nNikto is a command-line interface tool that runs on Linux. For those of us who are in a Windows-\ncentric environment, or prefer to use a graphical interface, SensePost has produced a Windows \nversion of Nikto called Wikto, as shown in Figure 5. Wikto is very similar in functionality to Nikto \nand provides us with a GUI.", "chunk_id": "66b222fd-62ba-411c-bc9e-34408ec79bb1", "chroma:document": "centric environment, or prefer to use a graphical interface, SensePost has produced a Windows \nversion of Nikto called Wikto, as shown in Figure 5. Wikto is very similar in functionality to Nikto \nand provides us with a GUI."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 9076c859-607e-453b-9496-2c6666b8bb73
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 163, "full_page_content": "164 \n \n \nFig 5 Wikto \n \n5.6.2.2 Burp Suite  \nQuite a few commercial Web analysis tools are also available, and they vary in price from several \nhundred dollars to many thousands of dollars. Burp Suite is one such tool, tending toward the lower \nend of the cost scale for the professional version but still presenting a solid set of features. Burp Suite \nruns in a GUI interface, as shown in Figure 6, and, in addition to the standard set of features we might \nfind in any Web assessment product, includes several more advanced tools for conducting more in-\ndepth attacks.", "chunk_id": "a04009a4-c16b-48f2-9183-5f414f854a03", "chroma:document": "164 \n \n \nFig 5 Wikto \n \n5.6.2.2 Burp Suite  \nQuite a few commercial Web analysis tools are also available, and they vary in price from several \nhundred dollars to many thousands of dollars. Burp Suite is one such tool, tending toward the lower \nend of the cost scale for the professional version but still presenting a solid set of features. Burp Suite"}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 08cd5ae0-bbee-4bc1-a80e-89f11f077725
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 163, "full_page_content": "164 \n \n \nFig 5 Wikto \n \n5.6.2.2 Burp Suite  \nQuite a few commercial Web analysis tools are also available, and they vary in price from several \nhundred dollars to many thousands of dollars. Burp Suite is one such tool, tending toward the lower \nend of the cost scale for the professional version but still presenting a solid set of features. Burp Suite \nruns in a GUI interface, as shown in Figure 6, and, in addition to the standard set of features we might \nfind in any Web assessment product, includes several more advanced tools for conducting more in-\ndepth attacks.", "chunk_id": "2874c069-0646-4bd4-ab8c-cca2ddd76718", "chroma:document": "runs in a GUI interface, as shown in Figure 6, and, in addition to the standard set of features we might \nfind in any Web assessment product, includes several more advanced tools for conducting more in-\ndepth attacks."}


created_at: 2025-01-28 05:36:03
topic: persistent://default/default/a5c4f461-3901-4175-9ce9-937730884692
id: 3008194f-7da6-4ce7-a23e-4a0760760df5
encoding: FLOAT32
metadata:
{"producer": "Microsoft\u00ae Word 2019", "creator": "Microsoft\u00ae Word 2019", "creationdate": "2022-02-08T09:25:32+05:30", "source": "data/SITA1602.pdf", "file_path": "data/SITA1602.pdf", "total_pages": 165, "format": "PDF 1.7", "title": "", "author": "Jabez J", "subject": "", "keywords": "", "moddate": "2022-02-08T09:25:32+05:30", "trapped": "", "page": 164, "full_page_content": "165 \n \n \nFig 6 : Burb Suite \n \nBurp Suite is also available in a free version that allows the use of the standard scanning and \nassessment tools but does not include access to the more advanced features \nReferences \nJason Andress, Steven Winterfeld, \u201cThe Basics of Information Security\u201d, 2nd Edition, Elsevier, 2014.", "chunk_id": "d5bd4cc7-884a-4781-b0bc-df5dbbce85fc", "chroma:document": "165 \n \n \nFig 6 : Burb Suite \n \nBurp Suite is also available in a free version that allows the use of the standard scanning and \nassessment tools but does not include access to the more advanced features \nReferences \nJason Andress, Steven Winterfeld, \u201cThe Basics of Information Security\u201d, 2nd Edition, Elsevier, 2014."}


