Dissertation/ Thesis
Co-design for Security and Reliability
| Title: | Co-design for Security and Reliability |
|---|---|
| Authors: | Manzhosov, Evgeny |
| Publication Year: | 2025 |
| Collection: | Columbia University: Academic Commons |
| Subject Terms: | Computer science, Computer security--Computer programs, Data encryption (Computer science), Computer systems--Reliability, Hacking |
| Description: | Security is commonly defined as the preservation of three system properties: confidentiality, which is the ability to prevent an unauthorized party from reading data; integrity, which is the ability to prevent an unauthorized party from writing data; and availability, which is the ability of an authorized party to use the system free of interference from an unauthorized party. Simply put, security mechanisms and policies are designed to keep unauthorized parties out of the system. On the other hand, reliability is defined as a system’s ability to operate as intended under non-adversarial conditions. It is measured as the probability of producing correct outputs at any given time. In the design of the reliability technique, one assumes that things that cause reliability failures (e.g., cosmic rays) do not seek to bypass reliability-enhancing mechanisms and policies. On the other hand, security mechanisms are designed assuming the attackers will attempt to circumvent them by exploiting any design or implementation weaknesses. From the above definitions, it may appear that reliability mechanisms should be built after security mechanisms since non-adversarial conditions can be enabled only with strong security mechanisms. However, for security mechanisms to operate as intended, they need to do so under both adversarial and non-adversarial conditions; thus, security mechanisms themselves are required to be reliable. This creates a chicken-and-egg situation that can only be resolved by co-designing security and reliability techniques together. However, due to historical reasons and engineering rationales, reliability features and security solutions are designed in isolation, often competing for the same resources and leading to trade-offs that may compromise both system reliability and security. Moreover, security today is layered on top of reliability. A justification for this may be that a system has to become reliable for it to attract users and thus become attack-worthy: an unreliable system is as useless to ... |
| Document Type: | thesis |
| Language: | English |
| DOI: | 10.7916/2mmk-0v96 |
| Availability: | https://doi.org/10.7916/2mmk-0v96 |
| Accession Number: | edsbas.FBA383A3 |
| Database: | BASE |
| FullText | Text: Availability: 0 CustomLinks: – Url: https://doi.org/10.7916/2mmk-0v96# Name: EDS - BASE (ns324271) Category: fullText Text: View record from BASE |
|---|---|
| Header | DbId: edsbas DbLabel: BASE An: edsbas.FBA383A3 RelevancyScore: 900 AccessLevel: 3 PubType: Dissertation/ Thesis PubTypeId: dissertation PreciseRelevancyScore: 899.809631347656 |
| IllustrationInfo | |
| Items | – Name: Title Label: Title Group: Ti Data: Co-design for Security and Reliability – Name: Author Label: Authors Group: Au Data: <searchLink fieldCode="AR" term="%22Manzhosov%2C+Evgeny%22">Manzhosov, Evgeny</searchLink> – Name: DatePubCY Label: Publication Year Group: Date Data: 2025 – Name: Subset Label: Collection Group: HoldingsInfo Data: Columbia University: Academic Commons – Name: Subject Label: Subject Terms Group: Su Data: <searchLink fieldCode="DE" term="%22Computer+science%22">Computer science</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+security--Computer+programs%22">Computer security--Computer programs</searchLink><br /><searchLink fieldCode="DE" term="%22Data+encryption+%28Computer+science%29%22">Data encryption (Computer science)</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+systems--Reliability%22">Computer systems--Reliability</searchLink><br /><searchLink fieldCode="DE" term="%22Hacking%22">Hacking</searchLink> – Name: Abstract Label: Description Group: Ab Data: Security is commonly defined as the preservation of three system properties: confidentiality, which is the ability to prevent an unauthorized party from reading data; integrity, which is the ability to prevent an unauthorized party from writing data; and availability, which is the ability of an authorized party to use the system free of interference from an unauthorized party. Simply put, security mechanisms and policies are designed to keep unauthorized parties out of the system. On the other hand, reliability is defined as a system’s ability to operate as intended under non-adversarial conditions. It is measured as the probability of producing correct outputs at any given time. In the design of the reliability technique, one assumes that things that cause reliability failures (e.g., cosmic rays) do not seek to bypass reliability-enhancing mechanisms and policies. On the other hand, security mechanisms are designed assuming the attackers will attempt to circumvent them by exploiting any design or implementation weaknesses. From the above definitions, it may appear that reliability mechanisms should be built after security mechanisms since non-adversarial conditions can be enabled only with strong security mechanisms. However, for security mechanisms to operate as intended, they need to do so under both adversarial and non-adversarial conditions; thus, security mechanisms themselves are required to be reliable. This creates a chicken-and-egg situation that can only be resolved by co-designing security and reliability techniques together. However, due to historical reasons and engineering rationales, reliability features and security solutions are designed in isolation, often competing for the same resources and leading to trade-offs that may compromise both system reliability and security. Moreover, security today is layered on top of reliability. A justification for this may be that a system has to become reliable for it to attract users and thus become attack-worthy: an unreliable system is as useless to ... – Name: TypeDocument Label: Document Type Group: TypDoc Data: thesis – Name: Language Label: Language Group: Lang Data: English – Name: DOI Label: DOI Group: ID Data: 10.7916/2mmk-0v96 – Name: URL Label: Availability Group: URL Data: https://doi.org/10.7916/2mmk-0v96 – Name: AN Label: Accession Number Group: ID Data: edsbas.FBA383A3 |
| PLink | https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=edsbas&AN=edsbas.FBA383A3 |
| RecordInfo | BibRecord: BibEntity: Identifiers: – Type: doi Value: 10.7916/2mmk-0v96 Languages: – Text: English Subjects: – SubjectFull: Computer science Type: general – SubjectFull: Computer security--Computer programs Type: general – SubjectFull: Data encryption (Computer science) Type: general – SubjectFull: Computer systems--Reliability Type: general – SubjectFull: Hacking Type: general Titles: – TitleFull: Co-design for Security and Reliability Type: main BibRelationships: HasContributorRelationships: – PersonEntity: Name: NameFull: Manzhosov, Evgeny IsPartOfRelationships: – BibEntity: Dates: – D: 01 M: 01 Type: published Y: 2025 Identifiers: – Type: issn-locals Value: edsbas – Type: issn-locals Value: edsbas.oa |
| ResultId | 1 |