Difference between revisions of "Liability"

From MgmtWiki
Jump to: navigation, search
(Created page with "==Full Title or Meme== Legal Liability for software solutions has been avoided until 2023-03 by the use of the Contract of Adhesion which declaims all liability. ==Co...")
 
(Context)
 
Line 3: Line 3:
  
 
==Context==
 
==Context==
In 2023-03 President Biden issued a [https://www.whitehouse.gov/wp-content/uploads/2023/03/National-Cybersecurity-Strategy-2023.pdf  National  
+
* A workable standard for liability would include a rules-based floor and a process-based safe harbor; none of the existing frameworks for secure software development is sufficiently definitive, but the elements of floor and ceiling are readily at hand.<ref>Jim Dempsey, ''Standards for Software Liability: Focus on the Product for Liability, Focus on the Process for Safe Harbor'' (2023-01) https://s3.documentcloud.org/documents/24371794/krp-editsdempsey_sbd-paper_final_jan23.pdf</ref>
 +
* In 2023-03 President Biden issued a [https://www.whitehouse.gov/wp-content/uploads/2023/03/National-Cybersecurity-Strategy-2023.pdf  National  
 
Cybersecurity Strategy] that asserted that some sort of [[Liability]] was required.  It is unclear what form that might take.
 
Cybersecurity Strategy] that asserted that some sort of [[Liability]] was required.  It is unclear what form that might take.
  

Latest revision as of 12:31, 16 February 2024

Full Title or Meme

Legal Liability for software solutions has been avoided until 2023-03 by the use of the Contract of Adhesion which declaims all liability.

Context

Cybersecurity Strategy] that asserted that some sort of Liability was required. It is unclear what form that might take.

References

  1. Jim Dempsey, Standards for Software Liability: Focus on the Product for Liability, Focus on the Process for Safe Harbor (2023-01) https://s3.documentcloud.org/documents/24371794/krp-editsdempsey_sbd-paper_final_jan23.pdf