Bug 777593 (SOA-101) - Security test case definition - need to implement high-priority tests for SOA-P
Summary: Security test case definition - need to implement high-priority tests for SOA-P
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-101
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Tooling
Version: 4.2 IR4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 GA
Assignee: Len DiMaggio
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On: SOA-131 SOA-134
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-06 14:56 UTC by Len DiMaggio
Modified: 2008-02-05 20:31 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-05 20:31:34 UTC
Type: Task

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-101 0 None None None Never

Description Len DiMaggio 2007-11-06 14:56:10 UTC 
Date of First Response: 2007-11-07 06:41:13
project_key: SOA

We need to identify the highest priority security risks for the initial SOA-P release. Marc Schoenefeld will perform analysis and prepare paper listing risks - and will work with/assist QE to perform tests.
Comment 5 Len DiMaggio 2007-12-13 17:24:12 UTC 
Link: Added: This issue depends SOA-131
Comment 6 Len DiMaggio 2007-12-13 17:24:39 UTC 
Link: Added: This issue depends SOA-134
Comment 7 Len DiMaggio 2007-12-13 17:28:18 UTC 
Marc also suggested:

http://findbugs.sourceforge.net/

and

http://www.neurofuzz.com/modules/software/wsfuzzer.php

but - given our release date and dependence on EAP - we can only really start this type of scanning/testing and not complete it by GA.
Comment 8 Len DiMaggio 2007-12-13 18:23:16 UTC 
Link: Added: This issue is a dependency of JBQA-1257
Comment 9 Marc Schoenefeld 2008-02-04 19:11:27 UTC 
Link: Added: This issue depends SOA-389
Comment 10 Marc Schoenefeld 2008-02-04 19:13:20 UTC 
Link: Removed: This issue depends SOA-389
Note You need to log in before you can comment on or make changes to this bug.