diff --git a/x-suse-definitions-schema.xsd b/x-suse-definitions-schema.xsd
new file mode 100644
index 0000000..344b0e9
--- /dev/null
+++ b/x-suse-definitions-schema.xsd
@@ -0,0 +1,120 @@
+
+
+
+
+ The following is a proposal for the experimental tests, objects, and states that will support assessment of SUSE Linux. Each test is an extension of the standard test element defined in the Core Definition Schema. Through extension, each test inherits a set of elements and attributes that are shared amongst all OVAL tests. Each test is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different tests and their relationship to the Core Definition Schema is not outlined here.
+ The OVAL Schema is maintained by The MITRE Corporation and developed by the public OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.mitre.org.
+
+ Experimental Schema for SUSE Linux
+ 5.11
+ 5/28/2015 8:00:00 AM
+ Copyright (c) 2002-2013, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at http://oval.mitre.org/oval/about/termsofuse.html. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
+
+
+
+
+
+
+
+
+
+
+
+
+ The AppArmor Status Test is used to check properties representing the counts of profiles and processes as per the results of the "apparmor_status" or "aa-status" command.
+ It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references an apparmorstatus_object and the optional state element specifies the data to check.
+
+
+
+ apparmorstatus_test
+ apparmorstatus_object
+ apparmorstatus_state
+ apparmorstatus_item
+
+
+
+
+
+ - the object child element of a apparmorstatus_test must reference a apparmorstatus_object
+
+
+ - the state child element of a apparmorstatustest must reference a apparmorstatus_state
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The apparmorstatus_object element is used by an apparmorstatus test to define the different information about the current AppArmor polciy. There is actually only one object relating to AppArmor Status and this is the system as a whole. Therefore, there are no child entities defined. Any OVAL Test written to check AppArmor status will reference the same apparmorstatus_object which is basically an empty object element.
+
+
+
+
+
+
+
+
+
+
+
+ The AppArmor Status Item displays various information about the current AppArmor policy. This item maps the counts of profiles and processes as per the results
+ of the "apparmor_status" or "aa-status" command. Please refer to the individual elements in the schema for more details about what each represents.
+
+
+
+
+
+
+
+
+ Displays the number of loaded profiles
+
+
+
+
+ Displays the number of profiles in enforce mode
+
+
+
+
+ Displays the number of profiles in complain mode
+
+
+
+
+ Displays the number of processes which have profiles defined
+
+
+
+
+ Displays the number of processes in enforce mode
+
+
+
+
+ Displays the number of processes in complain mode
+
+
+
+
+ Displays the number of processes which are unconfined but have a profile defined
+
+
+
+
+
+
+
+
diff --git a/x-suse-system-characteristics-schema.xsd b/x-suse-system-characteristics-schema.xsd
new file mode 100644
index 0000000..f291f70
--- /dev/null
+++ b/x-suse-system-characteristics-schema.xsd
@@ -0,0 +1,74 @@
+
+
+
+
+ The following is a proposal for the experimental system characteristics that will support assessment of SUSE Linux. Each item is an extension of the standard item element defined in the Core System Characteristics Schema. Through extension, each item inherits a set of elements and attributes that are shared amongst all OVAL items. Each item is described in detail and should provide the information necessary to understand what each element and attribute represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between the different items and their relationship to the Core System Characteristics Schema is not outlined here.
+ The OVAL Schema is maintained by The MITRE Corporation and developed by the public OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.mitre.org.
+
+ Experimental Schema for SUSE System Characteristics
+ 5.11
+ 5/28/2015 8:00:00 AM
+ Copyright (c) 2002-2013, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at http://oval.mitre.org/oval/about/termsofuse.html. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The AppArmor Status Item displays various information about the current AppArmor policy. This item maps the counts of profiles and processes as per the results
+ of the "apparmor_status" or "aa-status" command. Each item extends the standard ItemType as defined in the oval-system-characteristics-schema and one should refer
+ to the ItemType description for more information.
+
+
+
+
+
+
+
+
+ Displays the number of loaded profiles
+
+
+
+
+ Displays the number of profiles in enforce mode
+
+
+
+
+ Displays the number of profiles in complain mode
+
+
+
+
+ Displays the number of processes which have profiles defined
+
+
+
+
+ Displays the number of processes in enforce mode
+
+
+
+
+ Displays the number of processes in complain mode
+
+
+
+
+ Displays the number of processes which are unconfined but have a profile defined
+
+
+
+
+
+
+
+