You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _data/data.yml
+43-4Lines changed: 43 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,10 @@ people:
15
15
photo: "img/people/justin_cappos.jpg"
16
16
interests: "Solving real world security problems in practice"
17
17
publications:
18
+
- name: "NDSS 2025"
19
+
link: "/papers/yelgundhalli_gittuf_ndss_2025.pdf"
18
20
- name: "ACSAC 2023"
19
-
link: "/paper/moore_artemis_2023.pdf"
21
+
link: "/papers/moore_artemis_2023.pdf"
20
22
- name: "USENIX Security 2019"
21
23
link: "/papers/torres-toto-usenix19.pdf"
22
24
- name: "AsiaCCS 2018"
@@ -415,7 +417,7 @@ people:
415
417
deployments: <a href="https://github.com/alyptik/cepl/">CEPL</a>, an interactive C read-eval-print loop.
416
418
417
419
- &aditya_sirish
418
-
name: "Aditya Sirish"
420
+
name: "Aditya Sirish A Yelgundhalli"
419
421
anchor: aditya_sirish
420
422
internal: true
421
423
role: "Ph.D. Candidate"
@@ -716,6 +718,9 @@ people:
716
718
since: 2024
717
719
photo: "img/people/patrick_zielinski.jpg"
718
720
interests: "Distributed systems, version control systems, and cryptography"
721
+
publications:
722
+
- name: "NDSS 2025"
723
+
link: "/papers/yelgundhalli_gittuf_ndss_2025.pdf"
719
724
720
725
people_cards:
721
726
- type: "Faculty"
@@ -731,7 +736,6 @@ people:
731
736
- type: "PhD. Students"
732
737
anchor: phd
733
738
people:
734
-
- *marina_moore
735
739
- *nick_renner
736
740
- *aditya_sirish
737
741
- *prasant_adhikari
@@ -760,6 +764,7 @@ people:
760
764
- type: Alumni
761
765
anchor: alumni
762
766
people:
767
+
- *marina_moore
763
768
- *lois_delong
764
769
- *preston_moore
765
770
- *yiwen_li
@@ -1327,19 +1332,51 @@ publications:
1327
1332
### DO NOT FORGET TO ADD YOUR NEW TAG &XXXXXX TO THE ENTRIES AT THE BOTTOM ###
1328
1333
### IF YOU FORGET, YOUR ENTRIES WILL NOT SHOW UP ON THE SITE! ###
1329
1334
1335
+
- &yelgundhalli_gittuf_ndss_2025
1336
+
anchor: yelgundhalli_gittuf_ndss_2025
1337
+
title: "Rethinking Trust in Forge-Based Git Security"
1338
+
authors:
1339
+
- name: "A.S.A. Yelgundhalli, P. Zielinski, R. Curtmola, J. Cappos"
1340
+
project: *gittuf
1341
+
booktitle: "Network and Distributed System Security Symposium 2025 (NDSS 2025)"
1342
+
year: "2025"
1343
+
pages: ""
1344
+
publisher: ""
1345
+
link: "/papers/yelgundhalli_gittuf_ndss_2025.pdf"
1346
+
abstract: "Git is the most popular version control system today, with Git forges such as GitHub, GitLab, and Bitbucket used to add functionality. Significantly, these forges are used to enforce security controls. However, due to the lack of an open protocol for ensuring a repository’s integrity, forges cannot prove themselves to be trustworthy, and have to carry the responsibility of being non-verifiable trusted third parties in modern software supply chains.
1347
+
1348
+
In this paper, we present gittuf, a system that decentralizes Git security and enables every user to contribute to collectively enforcing the repository’s security. First, gittuf enables distributing of policy declaration and management responsibilities among more parties such that no single user is trusted entirely or unilaterally. Second, gittuf decentralizes the tracking of repository activity, ensuring that a single entity cannot manipulate repository events. Third, gittuf decentralizes policy enforcement by enabling all developers to independently verify the policy, eliminating the single point of trust placed in the forge as the only arbiter for whether a change in the repository is authorized. Thus, gittuf can provide strong security guarantees in the event of a compromise of the centralized forge, the underlying infrastructure, or a subset of privileged developers trusted to set policy. gittuf also implements policy features that can protect against unauthorized changes to branches and tags (i.e., pushes) as well as files/folders (i.e., commits). Our analysis of gittuf shows that its properties and policy features provide protections against previously seen version control system attacks. In addition, our evaluation of gittuf shows it is viable even for large repositories with a high volume of activity such as those of Git and Kubernetes (less than 4% storage overhead and under 0.59s of time to verify each push).
1349
+
1350
+
Currently, gittuf is an OpenSSF sandbox project hosted by the Linux Foundation. gittuf is being used in projects hosted by the OpenSSF and the CNCF, and an enterprise pilot at Bloomberg is underway."
1351
+
1330
1352
- &covsbom_issre_2024
1331
1353
anchor: covsbom_issre_2024
1332
1354
title: "CovSBOM: Enhancing Software Bill of Materials with Integrated Code Coverage Analysis"
1333
1355
authors:
1334
1356
- name: "Y. Zhao, Y. Zhang, D. Chacko, J. Cappos."
1335
1357
project:
1336
-
booktitle: "The 35th IEEE International Symposium on Software Reliability Engineering (ISSRE 2023)"
1358
+
booktitle: "The 35th IEEE International Symposium on Software Reliability Engineering (ISSRE 2024)"
1337
1359
year: "2024"
1338
1360
pages: ""
1339
1361
publisher: ""
1340
1362
link: "/papers/covsbom_issre_2024.pdf"
1341
1363
abstract: "The widespread integration of open-source software into commercial codebases, government systems, and critical infrastructure presents significant security challenges, particularly due to the inclusion of vulnerable components. Software Bills of Materials (SBOMs) are crucial for tracking these components; however, they lack detailed insights into the actual utilization of each component, thereby limiting their effectiveness in vulnerability management. This paper introduces CovSBOM, a novel tool that integrates code coverage analysis into SBOMs to provide enhanced transparency and facilitate precise vulnerability detection. CovSBOM addresses the gap between current SBOM and security scanning tools by providing detailed insights into which parts of third-party libraries are actually being used, thereby reducing inefficiencies and the misallocation of developer resources caused by overemphasizing irrelevant vulnerabilities. Through a comprehensive evaluation of 23 large-scale applications, encompassing 1,614 dependencies and 145 vulnerability alerts, CovSBOM has demonstrated a significant reduction in false positives, accurately identifying 105 such instances. This improvement enhances the precision of vulnerability detection by approximately 72%, while effectively maintaining a reasonable level of scalability and usability."
- name: "M. Moore, A.S.A. Yelgundhalli, J. Cappos"
1370
+
project: *uptane
1371
+
booktitle: "Symposium on Vehicles Security and Privacy (VehicleSec) 2024"
1372
+
year: "2024"
1373
+
pages: ""
1374
+
publisher: ""
1375
+
link: "/papers/moore_scudo_vehiclesec_2024.pdf"
1376
+
abstract: "Software supply chain attacks are a major concern and need to be addressed by every organization, including automakers. While there are many effective technologies in both the software delivery and broader software supply chain security space, combining these technologies presents challenges specific to automotive applications. We explore the trust boundaries between the software supply chain and software delivery systems to determine where verification of software supply chain metadata should occur, how to establish a root of trust, and how supply chain policy can be distributed. Using this exploration, we design Scudo, a secure combination of software over the air and software supply chain security technologies. We show that adding full verification of software supply chain metadata on-vehicle is not only inefficient, but is also largely unnecessary for security with multiple points of repository-side verification.
1377
+
1378
+
In addition, this paper describes a secure instantiation of Scudo, which integrates Uptane, a state of the art software update security solution, and in-toto, a comprehensive supply chain security framework. A practical deployment has shown that Scudo provides robust software supply chain protections. The client side power and processing costs are negligible, with the updated metadata comprising 0.504% of the total update transmission. The client side verification adds 0.21 seconds to the total update flow. This demonstrates that Scudo is easy to deploy in ways that can efficiently and effectively catch software supply chain attacks."
0 commit comments