107 Publications (Page 4 of 5)
2019
Challenges with responding to static analysis tool alertsImtiaz, N.⋅Rahman, A.⋅Farhana, E. and Williams, L.(pp. 245-249)
Characterizing Attacker Behavior in a Cybersecurity Penetration Testing CompetitionMunaiah, N.⋅Rahman, A.⋅Pelletier, J.⋅Williams, L. and Meneely, A.
Security Smells in Infrastructure as Code ScriptsRahman, A.⋅Rayhanur Rahman, Md.⋅Parnin, C. and Williams, L.
Snakes in Paradise?: Insecure python-related coding practices in stack overflowRahman, A.⋅Farhana, E. and Imtiaz, N.(pp. 200-204)
Source code properties of defective infrastructure as code scriptsRahman, A. and Williams, L.Information and Software Technology, vol. 112, pp. 148-163.
| Journal Article
Synthesizing Program Execution Time Discrepancies in Julia Used for Scientific SoftwareFarhana, E.⋅Imtiaz, N. and Rahman, A.(pp. 496-500)
The Seven Sins: Security Smells in Infrastructure as Code ScriptsRahman, A.⋅Parnin, C. and Williams, L.(pp. 164-175)
2018
Anti-Patterns in Infrastructure as CodeRahman, A.(pp. 434-435)
Bugs in infrastructure as codeRahman, A.⋅Elder, S.⋅Shezan, F.H.⋅Frost, V.⋅Stallings, J. and Williams, L.
Characteristics of defective infrastructure as code scripts in DevOpsRahman, A.(pp. 476-479)
Characterizing Defective Configuration Scripts Used for Continuous DeploymentRahman, A. and Williams, L.(pp. 34-45)
Characterizing the influence of continuous integration: Empirical results from 250+ open source and proprietary projectsRahman, A.⋅Agrawal, A.⋅Krishna, R. and Sobran, A.(pp. 8-14)
Comprehension effort and programming activities: Related? or not related?Rahman, A.(pp. 66-69)
Poster: Defect prediction metrics for infrastructure as code scripts in DevOpsRahman, A.⋅Stallings, J. and Williams, L.(pp. 414-415)
Source code properties of defective infrastructure as code scriptsRahman, A. and Williams, L.
We don’t need another hero?: The impact of "heroes" on software developmentAgrawal, A.⋅Rahman, A.⋅Krishna, R.⋅Sobran, A. and Menzies, T.(pp. 245-253)
What is the connection between issues, bugs, and enhancements?: Lessons learned from 800+ software projectsKrishna, R.⋅Agrawal, A.⋅Rahman, A.⋅Sobran, A. and Menzies, T.(pp. 306-315)
What questions do programmers ask about configuration as code?Rahman, A.⋅Partho, A.⋅Morrison, P. and Williams, L.(pp. 16-22)
Where are the gaps? a systematic mapping study of infrastructure as code researchRahman, A.⋅Mahdavi-Hezaveh, R. and Williams, L.
2017
Characterizing scientific reporting in security literature: An analysis of ACM CCS and IEEE S&P papersBurcham, M.⋅Al-Zyoud, M.⋅Carver, J.C.⋅Alsaleh, M.⋅Du, H.⋅Gilani, F.⋅Jiang, J.⋅Rahman, A.⋅Kafali, Ö.⋅Al-Shaer, E. and Williams, L.(pp. 13-23)
Characterizing the influence of continuous integration: Empirical results from 250+ open source and proprietary projectsRahman, A.⋅Agrawal, A.⋅Krishna, R. and Sobran, A.
Predicting Android Application Security and Privacy Risk with Static Code MetricsRahman, A.⋅Pradhan, P.⋅Partho, A. and Williams, L.(pp. 149-153)
We don?t need another hero? The impact of ?Heroes? on software developmentAgrawal, A.⋅Rahman, A.⋅Krishna, R.⋅Sobran, A. and Menzies, T.
What is the connection between issues, bugs, and enhancements? (Lessons Learned from 800+ Software Projects)Krishna, R.⋅Agrawal, A.⋅Rahman, A.⋅Sobran, A. and Menzies, T.