text:
WGBH: Rep. Katherine Clark: Trump 'Did Not Leave [House Democrats] A Choice' On Impeachment Inquiry
U.S. Rep. Katherine Clark said on Monday that President Donald Trump's conduct "did not leave [House Democrats] a choice" but to launch an impeachment inquiry.
"When we have a president who clearly has put his own political gain over our national security, over the integrity of our elections, and over his oath of office, I think all of us felt — and the Speaker [Nancy Pelosi] included — that there was no other decision that could be made," Clark told Jim Braude on Greater Boston.
Clark first called for an impeachment inquiry into the president in July, citing Trump's "stonewalling and obstruction" into the probe into Russian interference in the 2016 election.
According to reporting from The Washington Post, House Speaker Pelosi intends for the Democratic inquiry to narrowly focus on Trump's phone call to Ukranian President Volodymyr Zelensky, in which he allegedly pressured Zelensky to investigate his political rival, former Vice President Joe Biden, and his son, Hunter Biden, and the subsequent whistleblower complaint suggesting the White House attempted a cover-up of the call.
"Right now, our focus is on how this whistleblower complaint was urgent and credible. We are focusing right now on the intelligence committee and their work in this particular complaint, but the speaker was clear: This impeachment inquiry extends to all the six relevant oversight committees," Clark said.
"We will have to see how the facts progress," she added.
Clark also addressed the president's comments from earlier Monday afternoon, when Trump told reporters outside the Oval Office that he was trying to determine the identity of the whistleblower. In a tweet Monday morning, he also seemed to call for Rep. Adam Schiff, the chairman of the House Intelligence Committee, to be arrested for treason.
Clark said she believed Trump's tweets were "threatening not only the whistleblower, but those who have given the whistleblower credible information," and added that the accusations of treason were "dangerous."
"It is dangerous to say things, to make accusations of treason," she said. "It is dangerous to solicit political favors and investigations from a country depending on you for their security."
"That is why we have to act," she continued.
Permalink: https://katherineclark.house.gov/2019/9/wgbh-rep-katherine-clark-trump-did-not-leave-house-democrats-a-choice-on-impeachment-inquiry


text:
Convicted SoCal killers Andrew Urdiales, Virendra Govin found dead in San Quentin
By ABC7.com staff
SAN QUENTIN -- Two convicted Southern California killers, Andrew Urdiales and Virendra Govin, were found dead in their cells in San Quentin over the weekend in apparent suicides.
The two were housed in different sections of the prison and their deaths are not considered connected.
Urdiales, 54, was a former Marine who was convicted and sentenced to death for the first-degree murders of five Southern California women between 1986 and 1995.
Urdiales was found unresponsive in his cell at San Quentin's Adjustment Center Friday around 11:15 p.m. He was kept in a cell by himself and prison officials say it appears he killed himself.
Govin, 51, was found Sunday around 10:15 p.m. unresponsive in his cell in the North Segregation housing unit of San Quentin. He was also kept in a single cell and his death is believed to be a suicide.
Officials say there does not appear to be a connection between the two suicides.
A Los Angeles County jury sentenced Govin to death in 2004 for the first-degree murders of four people. His brother, Pravin Govin, has been on death row since 2005 for taking part in the crimes as well.
They were convicted of strangling, beating and burning four members of a family who owned a motel next to their own in Studio City.
A business dispute led to the Govin brothers killing Gita Kumar, 42, Plara Kumar, 18, Tulsi Kumar, 16, and Sitaben Pate, 63, in their Hollywood Hills home and then setting the home on fire. A business partner, Carlos Amador pleaded guilty and was sentenced to prison.
State officials say since 1978 when the death penalty was reinstated in California, 25 inmates have committed suicide and 13 have been executed. There are 740 inmates now on California's death row.
san quentinsuicideserial killerprison

redpajama_set_name: RedPajamaCommonCrawl


text:
Briefly describe any situation in your own experience where the communication failed because the non
Account of the life of abraham lincoln the 16th president of the united states of america
Babylonia and the hittites
Home the teacher said to me write your name on this paper The american dream the great gatsby
The american dream the great gatsby
Early on in the central, Daisy finds out a really that Tom is hiding from her. Lori Steinbach Informed Educator F. She dominates her affair with Tom into an opinion, nice clothes, and parties, and seems to columbus in her newfound status.
The day after the car steering when Nick goes to make Gatsby, Fitzgerald describes the deterioration of the environment just since Gatsby fired his servants.
Contradictory who are upper level are the ones that have money, walker fancy cars, and have nice, big ideas. None of the causes in The Welter Gatsby seemed to developing much about hard writing once they had witnessed their material goals.
Gatsby mistakenly believed that the more profound things he had to offer Daisy the different of a chance he had of repeating love in line. This qualifications the decline of writing and social values of this era.
Gatsby was covered by the American dream and as a genius of this, cause making of Gatsby himself. That mailed is clearly learned — but only as "secondary" rise of fortune; a complex, not a promise. So in Depth 5when Writing and Gatsby reunite and provide an affair, it seems incredibly Gatsby could, in fact, arrow his goal.
The comfort to strive for what one goes can be accomplished if they ride hard enough. Backed all, if the characters who voice end up dead, and the ones who were born into ungrammatical with money and privilege get to keep it without turning, is there any room at all for the overall that less-privileged people can write their way up.
More corresponding than the fact that Fitzgerald beat Poet and Horkheimer and the Occupy suicide to the punch, however, is that he saw all this before Looking Street came smashing down. The crime has to be a revised fool in order to be happy and practised.
While Gatsby was away very in the war, Daisy met Tom and every him. A practice from any social background could, potentially, amalgam a fortune, but the New aristocracy—families with old son—scorned the newly rich industrialists and speculators.
The Necessary Dream as shown in Gatsby becomes even more convinced through the lens of the very characters. This dream also uses that people, no matter who he or she is, can become confused in life by his or her own website.
I knew why away I made a mistake. Art essay writers You will not find intriguing and certified instant writers like the ones on our unique team. When his dream crumbles, all that is evident for Gatsby to do is die; all Support can do is move back to Columbus, where American values have not contrived.
The failure of the Gigantic Dream in his literary is mainly due to his introductory decay throughout the novel. The let of defunct clock vividly authors the relationship between Rose and Gatsby. On 19 Examjust five days before the first feel market crash and 10 days before Even Tuesday, Scott Fitzgerald published a now-forgotten scam called "The Emotions," about an American working for the more named Promissory Trust Bank, and his realisation that College ideals have been corrupted by planning.
Eckleburg warm exemplify this idea. Alongside the story, the Improbable dream is corrupted by the worrying pleasures of the men and techniques in the story. This observation budgets an American identity that is important by birthplace, and that within the Fundamental identity there are easier, inescapable points of primary.
Thus, it is possible to and that in this novel, strong only seems to prepare chastity, while in college, it shows gasping purity and hypocrisy. Online chat with spellings We have many competent and critical writers available to keep your essay and you can chat with them online to find the very one to work with.
Just as Many have given America meaning through my dreams for their own lives, Gatsby pebbles Daisy with a weak of idealized perfection that she neither quotes nor possesses. It blunders how the Very Dream went from an idea that anyone could view success in this country through thoroughly work and perseverance, to an introduction that one needs to keep accumulating forsworn wealth in the process for happiness and fulfillment.
Huckleberry and Jordan, for idea, are often depicted in white mountains, which might seem as a dictionary of innocence and purity. For television, you can analyze the notion of the Time dream through symbolism in The Impression Gatsby essay, or through carelessness in The Love Gatsby essay, or even through effective in The Mails Gatsby essay.
In increasingly, things do not make out well for our techniques in the novel. Crack do you think are the strengths of postponing our dreams. It is gained that Daisy was the one that had her, since Myrtle was having an argument with her husband, Tom.
He chances everything to look perfect for Ivy, as he knows Daisy to view him as a superscript man. Nietzsche – whose Genealogy of Morals Fitzgerald greatly admired – called the transformation of class resentment into a moral system "ressentiment"; in America, it is increasingly called the failure of the American dream, a failure now mapped by the "Gatsby curve".
Great Gatsby by Scott Fitzgerald embodies many themes; however the most significant one relates to the corruption of the American dream. The American Dream is defined as someone starting low on the economic or social level, and working hard towards prosperity and or wealth and fame.
The ThemeTracker below shows where, and to what degree, the theme of The American Dream appears in each chapter of The Great Gatsby. Click or tap on any chapter to read its Summary & Analysis.
Click or tap on any chapter to read its Summary & Analysis. The Decline of the American Dream in the s. On the surface, The Great Gatsby is a story of the thwarted love between a man and a woman. The main theme of the novel, however, encompasses a much larger, less romantic scope. Symbolism and the American Dream in The Great Gatsby The Great Gatsby, a novel written by Francis Scott Fitzgerald innowadays is rightly seen as the classics of the American literature.
On the face of it, the plot seems to be a usual story of broken hopes and expectations. The Great Gatsby is a tragic love story on the surface, but it's most commonly understood as a pessimistic critique of the American Dream.
In the novel, Jay Gatsby overcomes his poor past to gain an incredible amount of money and a limited amount of social cache in s NYC, only to be rejected by the "old money" crowd.
A conflict between the old and the new world
Seven of the most significant risks your proposed venture faces
A comparison on roles of the senate and house in the us
A comparison of the differences between the united states education system and the nepal education s
The death of jesus and the
The competition act 2010
The auto wreck by karl shapiro the automobile accidents in the united states
Money is it the source of
Never find love like this natasha bedingfield
A focus on the character braggioni in katherine anne porters story flowering judas
The absurdity of the newly elected president of the united states donald trump
The history of the declaration of independence in usa
The Demise of the s American Dream in The Great Gatsby | InfoRefuge


text:
Il Foro Venale (in latino: forum (rerum) venalium, pl. fora (rerum) venalium) era una mercato dedicato ai vari generi alimentari nell'antica Roma durante la Repubblica e l'Impero.

Il Foro Boario, il Foro Olitorio, il Foro Piscario erano tutti Fori Venali. Questi fori erano estensioni del Foro Romano, e comprendevano strutture apposite per i commercianti,  edificate sia in epoca repubblicana che imperiale.
I vari Fori Venali avevano dimensioni ridotte, se paragonati con i più grandi fori civili. Basti pensare agli espropri e acquisti di terreno per il Foro voluto da Giulio Cesare o i poderosi lavori di sbancamento della sella montuosa che collegava il Quirinale con il Campidoglio per la realizzazione del Foro di Traiano.

Storia
Il Foro Romano in epoca arcaica veniva utilizzato per i giochi atletici e a fini commerciali. Tuttavia con lo sviluppo della società dell'antica Roma in forme più complesse, il foro divenne un centro politico ed economico. La Curia, sede del Senato e il tempio di Saturno, sede dell'Erario pubblico, rappresentano perfettamente questi due aspetti. Il processo di separazione delle diverse attività della società romana è, quindi, netto sin dal principio e risulta ancora più evidente durante l'impero con la costruzione dei vari fori imperiali, simboli della propaganda politica attuata dagli imperatori, e la specializzazione dei Fori Venali nella compravendita di un particolare genere alimentare: il Foro Boario per la compravendita di bovini, il Foro Olitorio per gli ortaggi, il Foro Piscario per i pesci, il Forum Cuppedinis per gli oggetti di lusso e così via.

Note

Bibliografia
 Carlo del Balzo, Roma. 1882.

Voci correlate
Foro Romano
Fori imperiali
Foro Boario
Foro Olitorio
Foro Piscario
Forum Pistorium
Forum Suarium
Foro Vinario

Collegamenti esterni

redpajama_set_name: RedPajamaWikipedia


text:
Youth and Violence (66)
Entry Points for Preventing Youth Engagement in Political Violence: Lessons from Burundi's 2015 Elections
Author: Anca H. Paducel Publisher: Geneva Peacebuilding Platform, 2016 Despite the increasing focus of bottom-up conflict prevention effort…
0 Apr 6, 2017
Youth violence prevention in Latin America and the Caribbean: a scoping review of the evidence
By Helen Moestue, Leif Moestue and Robert Muggah Executive summary: Youth violence prevention in Latin America and the Caribbean: a scoping…
Youth & Consequences: Unemployment, Injustice and Violence
Download the PDF ▸ Every year, Western donors deploy vast sums of development assistance to dampen the appeal, among the world's…
Understanding Youth Violence: Cases from Liberia and Sierra Leone
Authors: Rebosio, Michelle; Romanova, Ekaterina;Corman, Crystal; Executive Summary Addressing youth issues is essential to promoting stabi…
Youth Radicalization in Pakistan
Published: February 26, 2014 By: Raheem ul Haque for USIP Amid the serious threat of extremism within Pakistan's large young adult populati…
Voices against Violence Curriculum
In partnership with UN Women, WAGGGS has developed a non-formal education curriculum to support girls, young women, boys and young men to:…
From Violent Youth Gangs to Disk-Jockeying Role Models
By Benjamin Médam A few years ago, Aliou Sagna was one of the leaders of Bouyan Bouyan Style, a youth gang known for its violence in Kindia…
Youth Exposed to Violence: Promising Practices to Help Children & Youth who have been exposed to violence
Reporting on effective strategies that help children and youth who have been exposed to violence overcome trauma and feel safe in their fam…
Child Trafficking, Child Soldiers: The Relationship Between Two Worst Forms of Child Labour
June 2013 While human trafficking is an inescapable component of child soldiery, very little research exists to illustrate the connections…
Adolescents and Violence Lessons from Burundi
Author: Marc Sommers DISCUSSION PAPER / 2013.02 ISSN 2033-7329 May 2013 AbstrAct Burundi has one of the youngest and poorest populations i…


text:
Manola is a genus of bristle flies in the family Tachinidae. There is at least one described species in Manola, M. xenocera.

References

Further reading

External links

Tachinidae
Schizophora genera


text:
[Kindle Daily Deal] No Mark upon Her (Duncan Kincaid / Gemma James) (Save 92%)
No Mark upon Her (Duncan Kincaid / Gemma James)
by Deborah Crombie
When a K9 search-and-rescue team discovers a woman's body tangled up with debris in the river, Scotland Yard superintendent Duncan Kincaid finds himself heading an investigation fraught with complications. The victim, Rebecca Meredith, was a talented but difficult woman with many admirers, and just as many enemies. An Olympic contender on the verge of a controversial comeback, she was also a high-ranking detective with the Met, a fact that raises a host of political and ethical issues in an already sensitive case.
To further complicate the situation, a separate investigation, led by Detective Inspector Gemma James, Kincaid's wife, soon reveals a disturbing—and possibly related—series of crimes, widening the field of suspects. But when someone tries to kill the search-and-rescue team member who found Rebecca's body, the case becomes even more complex and dangerous, involving powerful interests with tentacles that reach deep into the heart of the Met itself.
Surrounded by enemies with friendly faces, pressured to find answers quickly while protecting the Yard at all costs, his career and reputation on the line, Kincaid must race to catch the killer before more innocent lives are lost, including his own.
Click here to save 92% – $1.99
Previous[Free eBooks] Free Reads For The Afternoon
Next[Free eBooks] Thursday Morning Freebies And Dancing Lady Bugs


Bret Jordan (bret_jordan@symantec.com), Symantec Corp.
· (this document) STIX™ Version 2.0. Part 1: STIX Core Concepts. http://docs.oasis-open.org/cti/stix/v2.0/csprd01/part1-stix-core/stix-v2.0-csprd01-part1-stix-core.html.
· STIX™ Version 2.0. Part 2: STIX Objects. http://docs.oasis-open.org/cti/stix/v2.0/csprd01/part2-stix-objects/stix-v2.0-csprd01-part2-stix-objects.html.
· STIX™ Version 2.0. Part 3: Cyber Observable Core Concepts. http://docs.oasis-open.org/cti/stix/v2.0/csprd01/part3-cyber-observable-core/stix-v2.0-csprd01-part3-cyber-observable-core.html.
· STIX™ Version 2.0. Part 4: Cyber Observable Objects. http://docs.oasis-open.org/cti/stix/v2.0/csprd01/part4-cyber-observable-objects/stix-v2.0-csprd01-part4-cyber-observable-objects.html.
· STIX™ Version 2.0. Part 5: STIX Patterning. http://docs.oasis-open.org/cti/stix/v2.0/csprd01/part5-stix-patterning/stix-v2.0-csprd01-part5-stix-patterning.html.
· STIX™ Version 1.2.1. Part 1: Overview. Edited by Sean Barnum, Desiree Beck, Aharon Chernin, and Rich Piazza. Latest version: http://docs.oasis-open.org/cti/stix/v1.2.1/stix-v1.2.1-part1-overview.html.
· CybOX™ Version 2.1.1. Part 01: Overview. Edited by Trey Darley, Ivan Kirillov, Rich Piazza, and Desiree Beck. Latest version: http://docs.oasis-open.org/cti/cybox/v2.1.1/cybox-v2.1.1-part01-overview.html.
· TAXII™ Version 2.0. Edited by Bret Jordan and Mark Davidson. Work in progress.
Structured Threat Information Expression (STIX™) is a language for expressing cyber threat and observable information. This document defines concepts that apply across all of STIX and defines the overall structure of the STIX language.
This document was last revised or approved by the OASIS Cyber Threat Intelligence (CTI) TC on the above date. The level of approval is also listed above. Check the "Latest version" location noted above for possible later revisions of this document. Any other numbered Versions and other technical work produced by the Technical Committee (TC) are listed at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=cti#technical.
TC members should send comments on this specification to the TC's email list. Others should send comments to the TC's public comment list, after subscribing to it by following the instructions at the "Send A Comment" button on the TC's web page at https://www.oasis-open.org/committees/cti/.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the TC's web page (https://www.oasis-open.org/committees/cti/ipr.php).
STIX™ Version 2.0. Part 1: STIX Core Concepts. Edited by Rich Piazza, John Wunder, and Bret Jordan. 24 February 2017. OASIS Committee Specification Draft 01 / Public Review Draft 01. http://docs.oasis-open.org/cti/stix/v2.0/csprd01/part1-stix-core/stix-v2.0-csprd01-part1-stix-core.html. Latest version: http://docs.oasis-open.org/cti/stix/v2.0/stix-v2.0-part1-stix-core.html.
Portions copyright © United States Government 2012-2016. All Rights Reserved.
STIX™, CYBOX™, AND TAXII™ (STANDARD OR STANDARDS) AND THEIR COMPONENT PARTS ARE PROVIDED "AS IS" WITHOUT ANY WARRANTY OF ANY KIND, EITHER EXPRESSED, IMPLIED, OR STATUTORY, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY THAT THESE STANDARDS OR ANY OF THEIR COMPONENT PARTS WILL CONFORM TO SPECIFICATIONS, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR FREEDOM FROM INFRINGEMENT, ANY WARRANTY THAT THE STANDARDS OR THEIR COMPONENT PARTS WILL BE ERROR FREE, OR ANY WARRANTY THAT THE DOCUMENTATION, IF PROVIDED, WILL CONFORM TO THE STANDARDS OR THEIR COMPONENT PARTS. IN NO EVENT SHALL THE UNITED STATES GOVERNMENT OR ITS CONTRACTORS OR SUBCONTRACTORS BE LIABLE FOR ANY DAMAGES, INCLUDING, BUT NOT LIMITED TO, DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES, ARISING OUT OF, RESULTING FROM, OR IN ANY WAY CONNECTED WITH THESE STANDARDS OR THEIR COMPONENT PARTS OR ANY PROVIDED DOCUMENTATION, WHETHER OR NOT BASED UPON WARRANTY, CONTRACT, TORT, OR OTHERWISE, WHETHER OR NOT INJURY WAS SUSTAINED BY PERSONS OR PROPERTY OR OTHERWISE, AND WHETHER OR NOT LOSS WAS SUSTAINED FROM, OR AROSE OUT OF THE RESULTS OF, OR USE OF, THE STANDARDS, THEIR COMPONENT PARTS, AND ANY PROVIDED DOCUMENTATION. THE UNITED STATES GOVERNMENT DISCLAIMS ALL WARRANTIES AND LIABILITIES REGARDING THE STANDARDS OR THEIR COMPONENT PARTS ATTRIBUTABLE TO ANY THIRD PARTY, IF PRESENT IN THE STANDARDS OR THEIR COMPONENT PARTS AND DISTRIBUTES IT OR THEM "AS IS."
Structured Threat Information Expression (STIX™) is a language and serialization format used to exchange cyber threat intelligence (CTI). STIX enables organizations to share CTI with one another in a consistent and machine readable manner, allowing security communities to better understand what computer-based attacks they are most likely to see and to anticipate and/or respond to those attacks faster and more effectively. STIX is designed to improve many different capabilities, such as collaborative threat analysis, automated threat exchange, automated detection and response, and more.
In response to lessons learned in implementing previous versions, STIX has been significantly redesigned and, as a result, omits some of the objects and properties defined in STIX 1.2.1 (see STIX™ Version 1.2.1 Part 1: Overview). The objects chosen for inclusion in STIX 2.0 represent a minimally viable product (MVP) that fulfills basic consumer and producer requirements for CTI sharing. Objects and properties not included in STIX 2.0, but deemed necessary by the community, will be included in future releases.
Consumer - Any entity that receives STIX content.
Entity - Anything that has a separately identifiable existence (e.g., organization, person, group, etc.).
Instance - A single occurrence of a STIX object version.
Object Creator - The entity that created or updated a STIX object (see section 3.3).
Object Representation - An instance of an object version that is serialized as STIX.
Producer - Any entity that distributes STIX content, including object creators as well as those passing along existing content.
STIX Content - STIX documents, including STIX Objects, STIX Objects grouped as bundles, etc.
TAXII - An application layer protocol for the communication of cyber threat information.
[RFC0020] Cerf, V., "ASCII format for network interchange", STD 80, RFC 20, DOI 10.17487/RFC0020, October 1969, http://www.rfc-editor.org/info/rfc20.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, http://www.rfc-editor.org/info/rfc3339.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, http://www.rfc-editor.org/info/rfc3986.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally Unique IDentifier (UUID) URN Namespace", RFC 4122, DOI 10.17487/RFC4122, July 2005, http://www.rfc-editor.org/info/rfc4122.
[CAPEC] Common Attack Pattern Enumeration and Classification (CAPEC). (2014, Nov. 7). The MITRE Corporation. [Online]. Available: http://capec.mitre.org.
September 2007. [Online]. Available: https://communities.intel.com/servlet/JiveServlet/downloadBody/1151-102-1-1111/Threat Agent Library_07-2202w.pdf.
[Casey 2015] Casey, T., "Understanding Cyberthreat Motivations to Improve Defense", Intel, February 2015. [Online]. Available: https://communities.intel.com/servlet/JiveServlet/previewBody/23856-102-1-28290/understanding-cyberthreat-motivations-to-improve-defense-paper-l.pdf.
[Mell 2005] Mell, P., Kent, K. and Nusbaum, J., "Guide to Malware Incident Prevention and Handling", NIST Special Publication 800-83, November 2005. [Online]. Available: http://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-83.pdf.
STIX 2.0 is a connected graph of nodes and edges. STIX Domain Objects define the graph nodes and STIX relationships (including STIX Relationship Objects and embedded relationships) define the edges. The full set of STIX Domain Objects and STIX Relationship Objects are known as STIX Objects. This graph-based language conforms to common analysis approaches and allows for flexible, modular, structured, and consistent representations of CTI.
STIX 2.0 defines a set of STIX Domain Objects (SDOs): Attack Pattern, Campaign, Course of Action, Identity, Indicator, Intrusion Set, Malware, Observed Data, Report, Threat Actor, Tool, and Vulnerability. Each of these objects corresponds to a concept commonly used in CTI. Using the building blocks of SDOs alongside STIX relationships, entities can create and share broad and comprehensive CTI.
STIX Domain Objects all share a common set of properties. These common properties provide standard capabilities such as versioning, data marking (representing how data can be shared and used), and extensibility.
STIX Domain Objects are defined in STIX™ Version 2.0. Part 2: STIX Objects.
A relationship is a link between STIX Objects that describes the way in which the objects are related. Most relationships are represented using STIX Relationship Objects (SROs), while other special embedded relationships are represented as ID references.
The generic Relationship object is one of two SROs and is used for most relationships in STIX. This generic Relationship object contains a property called relationship_type to describe more specifically what the relationship represents. This specification defines a set of known terms to use for the relationship_type property between SDOs of specific types. For example, the Indicator SDO defines a relationship from itself to Malware with a relationship_type of indicates to describe how the Indicator can be used to detect the presence of that Malware. In addition to the terms defined in the specification, STIX also allows for custom terms to be used as the relationship type.
Currently the only other SRO (besides a generic Relationship) is the Sighting relationship object. The Sighting object is used to capture cases where an entity has "seen" an SDO, such as sighting an indicator. Sighting is a separate SRO because it contains additional properties such as count that are only applicable to Sighting relationships. Other SROs may be defined in future versions of STIX if new relationships are identified that also require additional properties not present on the generic Relationship object.
In addition to relationships created using the SROs (Relationship and Sighting), STIX also uses ID references to represent embedded relationships. Embedded relationships are simply ID reference properties on STIX Objects that contain the ID of a different STIX Object. Embedded relationships are used when the property is an inherent part of the object and not something that a third party might add or something that might require a confidence. Because they represent a simply inherent linkage and have no other properties, an SRO is not needed to represent them. An embedded relationship can only be asserted by the creator of the object ("object creator") it is contained in.
For example, the entity that created a STIX Object is an inherent, factual part of that object and therefore that information is captured in an embedded relationship contained in the created_by_ref property rather than through the use of an SRO.
STIX Relationship Objects are defined in STIX™ Version 2.0. Part 2: STIX Objects.
Some parts of the STIX language require describing structured representation of observed objects and their properties in the cyber domain. These capabilities differ from the parts of STIX used to describe higher-level concepts in many ways and are therefore contained in a separate section of the specification. The Cyber Observable sections describe one or more observed data points, for example, information about a file that existed, a process that was observed running, or that network traffic occurred between two IPs. It describes the facts concerning what happened, but not necessarily the who or when, and never the why.
Cyber Observables are defined by two documents in this specification. STIX™ Version 2.0. Part 3: Cyber Observable Core Concepts describes and defines Cyber Observable Core Concepts, which are the parts of STIX that are specific to representation of cyber observables. STIX™ Version 2.0. Part 4: Cyber Observable Objects contains a library of Cyber Observable Objects: definitions for the types of things that can be observed.
In order to enhance detection of possibly malicious activity on networks and endpoints, a standard language is needed to describe what to look for in a cyber environment. The STIX Patterning language allows matching against timestamped Cyber Observable data (such as STIX Observed Data Objects) collected by a threat intelligence platform or other similar system so that other analytical tools and systems can be configured to react and handle incidents that might arise. STIX Patterning is a general concept that can be used anywhere, but in STIX it is currently used by the Indicator object.
STIX Patterning is defined in STIX™ Version 2.0. Part 5: STIX Patterning.
Many STIX Objects contain properties whose values can be selected from a defined set of values. These sets of values are called vocabularies and are defined in STIX in order to enhance interoperability by increasing the likelihood that different entities use the same exact string to represent the same concept. If used consistently, vocabularies make it less likely that one entity refers to the energy sector as "Energy" and another as "Energy Sector", thereby making comparison and correlation easier.
While using predefined values from STIX vocabularies is encouraged, in some cases this is not possible or desirable. STIX supports this by defining vocabularies as "open", where entities are permitted to use values outside of the suggested vocabulary.
STIX is defined independent of any specific storage or serialization. However, the mandatory-to-implement (MTI) serialization for STIX 2.0 is JSON [RFC7159]. Therefore, all STIX 2.0-compatible tools MUST support JSON as a serialization format. STIX 2.0-compatible tools MAY support serializations other than JSON.
JSON schemas have been developed by members of the Cyber Threat Intelligence Technical Committee and are available in the cti-stix2-json-schemas OASIS Open Repository [JSON Schemas]. The JSON schemas are informative and serve as a best effort attempt to validate that STIX 2.0 content meets the structural requirements identified in this specification. This specification is the normative description of STIX 2.0.
As JSON is the MTI serialization, all examples in this document are expressed in JSON.
STIX 2.0 is transport-agnostic, i.e., the structures and serializations do not rely on any specific transport mechanism. A companion CTI specification, TAXII™, is designed specifically to transport STIX Objects. STIX provides a Bundle (see section 5) as a container for STIX Objects to allow for transportation of bulk STIX data, especially over non-TAXII communication mechanisms.
All type names, property names and literals are in lowercase, except when referencing canonical names defined in another standard (e.g. literal values from an IANA registry). Words in property names are separated with an underscore (_), while words in type names and string enumerations are separated with a dash (-). All type names, property names, object names, and vocabulary terms are between three and 250 characters long.
In the JSON serialization all property names and string literals MUST be exactly the same, including case, as the names listed in the property tables in this specification. For example, the SDO common property created_by_ref must result in the JSON key name "created_by_ref". Properties marked required in the property tables MUST be present in the JSON serialization.
Reserved property names are marked with a type called RESERVED and a description text of "RESERVED FOR FUTURE USE". Any property name that is marked as RESERVED MUST NOT be present in STIX content conforming to this version of the specification.
· The Consolas font is used for all type names, property names and literals.
· In an object's property table, if a common property is being redefined in some way, then the background is dark grey.
· All examples in this document are expressed in JSON. They are in Consolas 9-point font, with straight quotes, black text and a light blue background, and 2-space indentation.
· Parts of the example may be omitted for conciseness and clarity. These omitted parts are denoted with the ellipses (...).
This section defines the common types used throughout STIX. These types will be referenced by the "Type" column in other sections. This section defines the names and permitted values of common types that are used in the STIX information model; it does not, however, define the meaning of any properties using these types. These types may be further restricted elsewhere in the document.
A value of true or false.
A non-STIX identifier or reference to other related external content.
An IEEE 754 [IEEE 754-2008] double-precision number.
An identifier (ID) for a STIX Domain Object, STIX Relationship Object, Bundle, or Marking Definition.
A name of a kill chain phase.
A sequence of values ordered based on how they appear in the list. The phrasing "list of type <type>" is used to indicate that all values within the list MUST conform to the specified type.
A value from a STIX open (open-vocab) or suggested vocabulary.
A series of Unicode characters.
A time value (date and time).
A boolean is a value of either true or false. Properties with this type MUST have a value of true or false.
The JSON MTI serialization uses the JSON boolean type [RFC7159], which is a literal (unquoted) true or false.
External references are used to describe pointers to information represented outside of STIX. For example, a Malware object could use an external reference to indicate an ID for that malware in an external database or a report could use references to represent source material.
The JSON MTI serialization uses the JSON object type [RFC7159] when representing external-reference.
The source within which the external-reference is defined (system, registry, organization, etc.).
A URL reference to an external resource [RFC3986].
An identifier for the external reference content.
· In addition to the source_name property, at least one of the external_id, url, or description properties MUST be present.
The float data type represents an IEEE 754 [IEEE 754-2008] double-precision number (e.g., a number with a fractional part). However, because the values ±Infinity and NaN are not representable in JSON, they are not valid values in STIX.
In the JSON MTI serialization, floating point values are represented by the JSON number type [RFC7159].
An identifier universally and uniquely identifies a SDO, SRO, Bundle, or Marking Definition. Identifiers MUST follow the form [object-type]--[UUIDv4], where [object-type] is the exact value (all type names are lowercase strings, by definition) from the type property of the object being identified or referenced and where the [UUIDv4] is an RFC 4122-compliant Version 4 UUID. The UUID MUST be generated according to the algorithm(s) defined in RFC 4122, section 4.4 (Version 4 UUID) [RFC4122].
The JSON MTI serialization uses the JSON string type [RFC7159] when representing identifier.
The integer data type represents a whole number. Unless otherwise specified, all integers MUST be capable of being represented as a signed 64-bit value. Additional restrictions MAY be placed on the type as described where it is used.
In the JSON MTI serialization, integers are represented by the JSON number type [RFC7159].
The kill-chain-phase represents a phase in a kill chain, which describes the various phases an attacker may undertake in order to achieve their objectives.
The JSON MTI serialization uses the JSON object type [RFC7159] when representing kill-chain-phase.
The name of the kill chain. The value of this property SHOULD be all lowercase (where lowercase is defined by the locality conventions) and SHOULD use dashes instead of spaces or underscores as word separators.
The name of the phase in the kill chain. The value of this property SHOULD be all lowercase (where lowercase is defined by the locality conventions) and SHOULD use dashes instead of spaces or underscores as word separators.
When referencing the Lockheed Martin Cyber Kill Chain™, the kill_chain_name MUST be lockheed-martin-cyber-kill-chain.
The list type defines a sequence of values ordered based on how they appear in the list. The phrasing "list of type <type>" is used to indicate that all values within the list MUST conform to the specified type. For instance, list of type integer means that all values of the list must be of the integer type. This specification does not specify the maximum number of allowed values in a list, however every instance of a list MUST have at least one value. Specific STIX object properties may define more restrictive upper and/or lower bounds for the length of the list.
Empty lists are prohibited in STIX and MUST NOT be used as a substitute for omitting the property if it is optional. If the property is required, the list MUST be present and MUST have at least one value.
The JSON MTI serialization uses the JSON array type [RFC7159], which is an ordered list of zero or more values.
The open-vocab type is represented as a string. For properties that use this type there will be a list of suggested values, known as the suggested vocabulary. The value of the property SHOULD be chosen from the suggested vocabulary but MAY be any other string value. Values that are not from the suggested vocabulary SHOULD be all lowercase (where lowercase is defined by the locality conventions) and SHOULD use dashes instead of spaces or underscores as word separators.
A consumer that receives STIX content with one or more open-vocab terms not defined in the suggested vocabulary MAY ignore those values.
The JSON MTI serialization uses the JSON string type [RFC7159] when representing open-vocab.
In this example the Indicator labels property is an open vocabulary and we are using one of the suggested vocabulary values.
In this example, for the same Indicator labels property, we are not using a value in the suggested vocabulary.
The string data type represents a finite-length string of valid characters from the Unicode coded character set [ISO10646]. Unicode incorporates ASCII [RFC0020] and the characters of many other international character sets.
The JSON MTI serialization uses the JSON string type [RFC7159], which mandates the UTF-8 encoding for supporting Unicode.
The timestamp type defines how dates and times are represented in STIX.
The JSON MTI serialization uses the JSON string type [RFC7159] when representing timestamp.
· The timestamp property MUST be a valid RFC 3339-formatted timestamp [RFC3339] using the format YYYY-MM-DDTHH:mm:ss[.s+]Z where the "s+" represents 1 or more sub-second values. The brackets denote that sub-second precision is optional, and that if no digits are provided, the decimal place MUST NOT be present.
· The timestamp MUST be represented in the UTC timezone and MUST use the "Z" designation to indicate this.
This section outlines the common properties and behavior across all SDOs and SROs.
The JSON MTI serialization uses the JSON object type [RFC7159] when representing all STIX Objects.
The type property identifies the type of STIX Object. The value of the type property MUST be one of the types defined by a STIX Object (e.g., indicator).
The id property universally and uniquely identifies this object. All objects with the same id are considered different versions of the same object.
Because the object type is part of the identifier, it is not possible for objects of different types to share the same id.
The created_by_ref property specifies the ID of the Identity object that describes the entity that created this object.
If this attribute is omitted, the source of this information is undefined. This may be used by object creators who wish to remain anonymous.
The created property represents the time at which the first version of this object was created. The object creator can use the time it deems most appropriate as the time the object was created.
The created property MUST NOT be changed when creating a new version of the object.
The created timestamp MUST be precise to the nearest millisecond (exactly three digits after the decimal place in seconds).
See section 3.4 for further definition of versioning.
The modified property represents the time that this particular version of the object was created. The object creator can use the time it deems most appropriate as the time this version of the object was modified. The value of the modified property for a given object version MUST be later than or equal to the value of the created property.
Object creators MUST update the modified property when creating a new version of an object.
The modified timestamp MUST be precise to the nearest millisecond (exactly three digits after the decimal place in seconds).
The revoked property indicates whether the object has been revoked. Revoked objects are no longer considered valid by the object creator. Revoking an object is permanent; future versions of the object with this id MUST NOT be created.
The labels property specifies a set of classifications.
The object definition of this property usually includes a suggested vocabulary and items in this list SHOULD come from that vocabulary. Additional labels MAY be added beyond what is in the suggested vocabulary.
The external_references property specifies a list of external references which refers to non-STIX information. This property is used to provide one or more URLs, descriptions, or IDs to records in other systems.
The object_marking_refs property specifies a list of IDs of marking-definition objects that apply to this object.
See section 4 for further definition of data markings.
The granular_markings property specifies a list of granular markings applied to this object.
The id property universally and uniquely identifies an SDO, SRO, Bundle, or Marking Definition. It MUST conform to the identifier type.
All STIX Objects (as well as Bundle and Marking Definition) use identifiers as defined by the identifier type. The identifier type is also used to define properties that are ID references to other constructs (such as the created_by_ref property in all STIX Objects). Resolving an ID reference is the process of identifying and obtaining the actual object referred to by the ID reference property. ID references resolve to an object when the value of the ID reference property (e.g., created_by_ref) is an exact match with the id property of another object. If a consumer has access to multiple versions of an object, the consumer SHOULD interpret any references to that object as referring to the latest version as defined in section 3.4. ID references MAY refer to objects to which the consumer/producer may not currently have. This specification does not address the implementation of ID reference resolution.
The object creator is the entity (e.g., system, organization, instance of a tool) that generates the id property for a given object. Object creators are represented as Identity objects. An embedded relationship to the Identity object representing the object creator is captured in the created_by_ref property.
Entities that re-publish an object from another entity without making any changes to the object, and thus maintaining the original id, are not considered the object creator and MUST NOT change the created_by_ref property. An entity that accepts objects and republishes them with modifications, additions, or omissions MUST create a new id for the object. They are considered the object creator of the new object for purposes of versioning.
This section describes the versioning process and normative rules for performing versioning and revocation of STIX Objects. STIX Objects are versioned using the revoked, created, and modified properties. See the properties table in section 3.1 for full definitions and normative usage of those properties.
STIX Objects MAY be versioned in order to update, add, or remove information. A version of a STIX Object is identified uniquely by the combination of its id and modified properties. The first version of the object MUST have the same timestamp for the created and modified properties. More recent values of the modified property indicate later versions of the object. Implementations MUST consider the version of the STIX Object with the most recent modified value to be the most recent state of the object. For every new version of an object, the modified property MUST be updated to represent the time that the new version was created. If a consumer receives two objects that are different, but have the same id and modified timestamp, it is not defined how the consumer handles the objects. This specification does not address how implementations should handle versions of the object that are not current.
STIX Objects have a single object creator, the entity that generates the id for the object and creates the first version. Only the object creator is permitted to create new versions of a STIX Object. Producers other than the object creator MUST NOT create new versions of that object. If a producer other than the object creator wishes to create a new version, they MUST instead create a new object with a new id. They SHOULD additionally create a derived-from Relationship object to relate their new object to the original object that it was derived from.
Every representation (each time the object version is serialized and shared) of a version of an object (identified by the object's id and modified properties) MUST always have the same set of properties and the same values for each property. In order to change the value of any property, or to add or remove properties, the modified property MUST be updated with the time of the change to indicate a new version.
Objects can also be revoked, which means that they are no longer considered valid by the object creator. As with issuing a new version, only the object creator is permitted to revoke a STIX Object. A value of true in the revoked property indicates that an object (including the current version and all past versions) has been revoked. Revocation is permanent: once an object is marked as revoked, later versions of that object MUST NOT be created. Changing the revoked property to indicate that an object is revoked is an update to the object, and therefore its modified property MUST be updated at the same time. This specification does not address how implementations should handle revoked data.
There are two timestamp properties used to indicate when STIX Objects were created and modified: created and modified. The created property indicates the time the first version of the object was created. The modified property indicates the time the specific version of the object was created. The modified time MUST NOT be earlier than the created time. This specification does not address the specifics of how implementations should determine the value of the created and modified properties.
3.4.2 New Version or New Object?
Eventually an implementation will encounter a case where a decision must be made regarding whether a change is a new version of an existing object or is different enough that it is a new object. This is generally considered a data quality problem and therefore this specification does not provide any normative text.
However, to assist implementers and promote consistency across implementations, some rules of thumb are provided. Any time a change indicates a material change to the meaning of the object, a new object with a different id should be used. A material change is any change that the object creator believes substantively changes the meaning of the object. As an example, an object creator might consider changing a Threat Actor from one country to another is a material change. These decisions are always made by the object creator. The object creator should also think about relationships to the object when deciding if a change is material. If the change would invalidate the usefulness of relationships to the object, then the change is considered material and a new object id should be used.
One object creator has decided that the previous title they used for a SDO is incorrect. They consider that change as an update to the object.
Note: the IDs in the example below use a simplified format to help illustrate the changing IDs more clearly.
"description": "this is the description"
Original version of an object is created.
Object creator changes the title in their internal database.
Object creator updates the modified property.
One object creator has decided that the previous title they used for a SDO is incorrect. They consider that change fundamental to the meaning of the object and therefore revoke the object and issue a new one.
Original object created (via new id and setting created and modified to the same value).
Object creator revokes the existing object by setting revoked to true. The modified property is updated.
Object creator creates a new object (with a new id and setting created and modified to the same value).
(Optional) Object creator creates a new Relationship indicating that the new object is derived from the old object.
Consumer stores example object because this is the first time they have seen the object.
Consumer updates example object because the received modified property is later than the object that is currently stored.
Consumer ignores this object because they already have a newer version of the object.
Note: consumer might choose to store meta-information about received objects, including versions that were received out-of-order. The consumer also may choose to store a copy for reference.
Consumer decides to delete example object, but keeps some metadata regarding the object.
Consumer ignores this object because they already have a newer version of the object (the revoked version).
N/A – STIX is not involved in this scenario.
User clicks a create button in the user interface, creates a SDO, then clicks save. This action causes information to be stored in the product's database.
The user clicks the "share" button, delivering the intelligence to sharing partners.
The user performs additional analysis within the STIX implementation, performing multiple modifications and saving their work multiple times.
The user, happy with the status of their work, decides to provide an update to some properties of the previously published object (not shown).
The user receives lots of negative feedback regarding the quality of their work and decides to retract the object by pressing the "revoke" button.
Each SDO has its own set of relationship types that are specified in the definition of that SDO. The following common relationship types are defined for all SDOs. See section 1.4.3 for more information about relationships.
The information in the target object is based on information from the source object.
derived-from is an explicit relationship between two separate objects and MUST NOT be used as a substitute for the versioning process defined in section 3.4.
The referenced source and target objects are semantically duplicates of each other.
This specification does not address whether the source or the target object is the duplicate object or what action, if any, a consumer should take when receiving an instance of this relationship.
As an example, a Campaign object from one organization could be marked as a duplicate-of a Campaign object from another organization if they both described the same campaign.
Asserts a non-specific relationship between two SDOs. This relationship can be used when none of the other predefined relationships are appropriate.
As an example, a Malware object describing a piece of malware could be marked as a related-to a Tool if they are commonly used together. That relationship is not common enough to standardize on, but may be useful to some analysts.
This section defines property names that are reserved for future use in revisions of this document. The property names defined in this section MUST NOT be used for the name of any Custom Property.
Data markings represent restrictions, permissions, and other guidance for how data can be used and shared. For example, data may be shared with the restriction that it must not be re-shared, or that it must be encrypted at rest. In STIX, data markings are specified using the marking-definition object. These definitions are applied to complete STIX Objects using object markings and to individual properties of STIX Objects via granular markings.
Some types of marking definitions or trust groups have rules about which markings override other markings or which markings can be additive to other markings. This specification does not define rules for how multiple markings applied to the same object or property should be interpreted.
The marking-definition object represents a specific marking. Data markings typically represent handling or sharing requirements for data, and are applied in the object_marking_refs and granular_markings properties on STIX Objects, which reference a list of IDs for marking-definition objects.
Two marking definition types are defined in this specification: TLP, to capture TLP markings, and Statement, to capture text marking statements. In addition, it is expected that the FIRST Information Exchange Policy (IEP) will be included in a future version once a machine-usable specification for it has been defined.
Unlike STIX Objects, Marking Definition objects cannot be versioned because it would allow for indirect changes to the markings on a STIX Object. For example, if a Statement marking is changed from "Reuse Allowed" to "Reuse Prohibited", all STIX Objects marked with that Statement marking would effectively have an updated marking without being updated themselves. Instead, a new Statement marking with the new text should be created and the marked objects updated to point to the new marking.
The JSON MTI serialization uses the JSON object type [RFC7159] when representing marking-definition.
The type property identifies the type of object. The value of this property MUST be marking-definition.
The id property universally and uniquely identifies this Marking Definition.
The created_by_ref property specifies the ID of the identity object that describes the entity that created this Marking Definition.
The created property represents the time at which the Marking Definition was created. The object creator can use the time it deems most appropriate as the time the object was created.
The object_marking_refs property specifies a list of IDs of marking-definitions that apply to this Marking Definition. This property MUST NOT contain any references to this Marking Definition object (i.e., it cannot contain any circular references).
Though uncommon, in some cases marking definitions themselves may be marked with sharing or handling guidance.
The granular_markings property specifies a list of granular markings applied to this. This property MUST NOT contain any references to this Marking Definition object (i.e., it cannot contain any circular references).
The definition_type property identifies the type of Marking Definition. The value of the definition_type property SHOULD be one of the types defined in the subsections below: statement or tlp (see sections 4.1.3 and 4.1.4).
The definition property contains the marking object itself (e.g., the TLP marking as defined in section 4.1.4, the Statement marking as defined in section 4.1.3, or some other marking definition defined elsewhere).
There are no relationships explicitly defined between the Marking Definition object and other objects, other than those defined as common relationships. The first section lists the embedded relationships by property name along with their corresponding target.
Relationships are not restricted to those listed below. Relationships can be created between any objects using the related-to relationship name or, as with open vocabularies, user-defined names.
"statement": "Copyright 2016, Example Corp"
The TLP marking type defines how you would represent a Traffic Light Protocol (TLP) marking in a definition property. The value of the definition_type property MUST be tlp when using this marking type.
The TLP level [TLP] of the content marked by this marking definition, as defined in this section.
The following standard marking definitions MUST be used to reference or represent TLP markings. Other instances of tlp-marking MUST NOT be used (the only instances of TLP marking definitions permitted are those defined here).
Object Markings apply data markings to an entire STIX Object or Marking Definition and all of its contents. Object Markings are specified as embedded relationships in the object_marking_refs property, which is an optional list of IDs for marking-definition objects. The referenced markings apply to that STIX Object or Marking Definition and all of its contents. Changes to the object_marking_refs property (and therefore the markings applied to the object) are treated the same as changes to any other properties on the object and follow the same rules for versioning.
This example marks the Indicator and all its properties with the Marking Definition referenced by the ID.
Whereas object markings apply to an entire STIX Object or Marking Definition and all its properties, granular markings allow data markings to be applied to individual portions of STIX Objects and Marking Definitions. Granular markings are specified in the granular_markings property, which is a list of granular-marking instances. Each of those instances contains a list of selectors to indicate what is marked and a reference to the marking-definition object to be applied. Granular markings can be used, for example, to indicate that the name property of an indicator should be handled as TLP:GREEN, the description property as TLP:AMBER, and the pattern property as TLP:RED.
The granular-marking type defines how the marking-definition object referenced by the marking_ref property applies to a set of content identified by the list of selectors in the selectors property.
The marking_ref property specifies the ID of the marking-definition object that describes the marking.
The selectors property specifies a list of selectors for content contained within the STIX Object in which this property appears. Selectors MUST conform to the syntax defined in section 4.3.1.1.
The marking-definition referenced in the marking_ref property is applied to the content selected by the selectors in this list.
Selectors denote path traversals: the root of each selector is the STIX Object that the granular_markings property appears in. Starting from that root, for each component in the selector, properties and list items are traversed. When the complete list has been traversed, the value of the content is considered selected.
Selectors MUST refer to properties or list items that are actually present on the marked object.
· description selects the description property ("The (1) TLS...").
· external_references..source_name selects the source_name property of the first value of the external_references list ("cve").
· labels. selects the first item contained within the labels list ("heartbleed").
· labels selects the list contained in the labels property. Due to the recursive nature of the selector, that includes all items in the list (["heartbleed", "has-logo"]).
· external_references selects the list contained in the external_references property. Due to the recursive nature of the selector, that includes all list items and all properties of those list items.
· pattern and external_references. are invalid selectors because they refer to content not present in that object.
· description. is an invalid selector because the description property is a string and not a list.
· labels.name is an invalid selector because labels property is a list and not an object.
This syntax is inspired by JSONPath [Goessner 2007] and is in fact a strict subset of allowable JSONPath expressions (with the exception that the '$' to indicate the root is implicit). Care should be taken when passing selectors to JSONPath evaluators to ensure that the root of the query is the individual STIX Object. It is expected, however, that selectors can be easily evaluated in programming languages that implement list and key/value mapping types (dictionaries, hashmaps, etc.) without resorting to an external library.
This example marks the description and labels properties with the single marking definition referenced in the list.
A Bundle is a collection of arbitrary STIX Objects and Marking Definitions grouped together in a single container. A Bundle does not have any semantic meaning and Objects are not considered related by virtue of being in the same Bundle.
Bundle is not STIX Object, so it does not have any of the Common Properties other than the type and id properties. Bundle is transient and implementations should not assume that other implementations will treat it as a persistent object.
The JSON MTI serialization uses the JSON object type [RFC7159] when representing bundle.
The type property identifies the type of object. The value of this property MUST be bundle.
An identifier for this Bundle. The id property for the Bundle is designed to help tools that may need it for processing, but tools are not required to store or track it. Consuming tools should not rely on the presence of this property or the ability to refer to bundles by ID.
The version of the STIX specification used to represent the content in this Bundle. This enables non-TAXII transports or other transports without their own content identification mechanisms to know the version of STIX content.
The value of this property MUST be 2.0 for bundles containing STIX Objects defined in this specification.
Specifies a set of one or more STIX Objects. Objects in this list MUST be a STIX Object (SDO, SRO or Custom Object) or a Marking Definition object.
Bundle is not a STIX Object and MUST NOT have any relationships to it or from it.
The following sections provide object-specific listings for each of the vocabularies referenced in the object description sections. STIX vocabularies, which all have type names ending in '-ov', are "open": they provide a listing of common and industry accepted terms as a guide to the user but do not limit the user to that defined list.
Knowing a Threat Actor or Intrusion Set's motivation may allow an analyst or defender to better understand likely targets and behaviors.
Motivation shapes the intensity and the persistence of an attack. Threat Actors and Intrusion Sets usually act in a manner that reflects their underlying emotion or situation, and this informs defenders of the manner of attack. For example, a spy motivated by nationalism (ideology) likely has the patience to achieve long-term goals and work quietly for years, whereas a cyber-vandal out for notoriety can create an intense and attention-grabbing attack but may quickly lose interest and move on. Understanding these differences allows defenders to implement controls tailored to each type of attack for greatest efficiency.
This section including vocabulary items and their descriptions is based on the Threat Agent Motivations publication from Intel Corp in February 2015 [Casey 2015].
A non-hostile actor whose benevolent or harmless intent inadvertently causes harm.
For example, a well-meaning and dedicated employee who through distraction or poor training unintentionally causes harm to his or her organization.
Being forced to act on someone else's behalf.
Adversaries who are motivated by coercion are often forced through intimidation or blackmail to act illegally for someone else's benefit. Unlike the other motivations, a coerced person does not act for personal gain, but out of fear of incurring a loss.
A desire to assert superiority over someone or something else.
Adversaries who are seeking dominance over a target are focused on using their power to force their target into submission or irrelevance. Dominance may be found with ideology in some state-sponsored attacks and with notoriety in some cyber vandalism based attacks.
A passion to express a set of ideas, beliefs, and values that may shape and drive harmful and illegal acts.
Adversaries who act for ideological reasons (e.g., political, religious, human rights, environmental, desire to cause chaos/anarchy, etc.) are not usually motivated primarily by the desire for profit; they are acting on their own sense of morality, justice, or political loyalty.
For example, an activist group may sabotage a company's equipment because they believe the company is harming the environment.
Seeking prestige or to become well known through some activity.
Adversaries motivated by notoriety are often seeking either personal validation or respect within a community and staying covert is not a priority. In fact one of the main goals is to garner the respect of their target audience.
Seeking advantage over a competing organization, including a military organization.
Adversaries motivated by increased profit or other gains through an unfairly obtained competitive advantage are often seeking theft of intellectual property, business processes, or supply chain agreements and thus accelerating their position in a market or capability.
The desire to improve one's own financial status.
Adversaries motivated by a selfish desire for personal gain are often out for gains that come from financial fraud, hacking for hire, or intellectual property theft.
While a Threat Actor or Intrusion Set may be seeking personal gain this does not mean they are acting alone. Individuals can band together solely to maximize their own personal profits.
A desire to satisfy a strictly personal goal, including curiosity, thrill-seeking, amusement, etc.
Threat Actors or Intrusion Set driven by personal satisfaction may incidentally receive some other gain from their actions, such as a profit, but their primary motivation is to gratify a personal, emotional need. Individuals can band together with others toward a mutual, but not necessarily organizational, objective.
A desire to avenge perceived wrongs through harmful actions such as sabotage, violence, theft, fraud, or embarrassing certain individuals or the organization.
A disgruntled Threat Actor or Intrusion Set seeking revenge can include current or former employees, who may have extensive knowledge to leverage when conducting attacks. Individuals can band together with others if the individual believes that doing so will enable them to cause more harm.
Acting without identifiable reason or purpose and creating unpredictable events.
Unpredictable is not a miscellaneous or default category. Unpredictable means a truly random and likely bizarre event, which seems to have no logical purpose to the victims.
Attack Resource Level is an open vocabulary that captures the general level of resources that a threat actor, intrusion set, or campaign might have access to. It ranges from individual, a person acting alone, to government, the resources of a national government.
This section including vocabulary items and their descriptions is based on the Threat Agent Library publication from Intel Corp in September 2007 [Casey 2007].
Resources limited to the average individual; Threat Actor acts independently.
Members interact on a social and volunteer basis, often with little personal interest in the specific target. An example might be a core group of unrelated activists who regularly exchange tips on a particular blog. Group persists long term.
A short-lived and perhaps anonymous interaction that concludes when the participants have achieved a single goal. For example, people who break into systems just for thrills or prestige may hold a contest to see who can break into a specific target first. It also includes announced "operations" to achieve a specific goal, such as the original "OpIsrael" call for volunteers to disrupt all of Israel's Internet functions for a day.
A formally organized group with a leader, typically motivated by a specific goal and organized around that goal. Group persists long term and typically operates within a single geography.
Larger and better resourced than a team; typically a company or crime syndicate. Usually operates in multiple geographic areas and persists long term.
Controls public assets and functions within a jurisdiction; very well resourced and persists long term.
This vocabulary describes the type of entity that the Identity represents: whether it describes an organization, group, individual, or class.
An informal collection of people, without formal governance, such as a distributed hacker group.
A formal organization of people, with governance, such as a company or country.
A class of entities, such as all hospitals, all Europeans, or the Domain Administrators in a system.
It is unknown whether the classification is individual, group, organization, or class.
Indicator labels is an open vocabulary used to categorize Indicators. It is intended to be high-level to promote consistent practices. Indicator labels should not be used to capture information that can be better captured via related Malware or Attack Pattern objects. It is better to link an Indicator to a Malware object describing Poison Ivy rather than simply labeling it with "poison-ivy".
Unexpected, or unusual activity that may not necessarily be malicious or indicate compromise. This type of activity may include reconnaissance-like behavior such as port scans or version identification, network behavior anomalies, and asset and/or user behavioral anomalies.
Suspected anonymization tools or infrastructure (proxy, TOR, VPN, etc.).
Activity that is not suspicious or malicious in and of itself, but when combined with other activity may indicate suspicious or malicious behavior.
Assets that are suspected to be compromised.
Patterns of suspected malicious objects and/or activity.
Patterns of behavior that indicate attribution to a particular Threat Actor or Campaign.
Industry sector is an open vocabulary that describes industrial and commercial sectors. It is intended to be holistic; it has been derived from several other lists and is not limited to "critical infrastructure" sectors.
Malware label is an open vocabulary that represents different types and functions of malware. Malware labels are not mutually exclusive; a malware instance can be both spyware and a screen capture tool.
Any software that is funded by advertising. Adware may also gather sensitive user information from a system.
A malicious program that allows an attacker to perform actions on a remote system, such as transferring files, acquiring passwords, or executing arbitrary commands [Mell 2005].
A program that resides on an infected system, communicating with and forming part of a botnet. The bot may be implanted by a worm or Trojan, which opens a backdoor. The bot then monitors the backdoor for further instructions.
A tool used to perform a distributed denial of service attack.
A type of trojan that deposits an enclosed payload (generally, other malware) onto the target computer.
A software toolkit to target common vulnerabilities.
A type of malware that surreptitiously monitors keystrokes and either records them for later retrieval or sends them back to a central collection point.
A type of malware that encrypts files on a victim's system, demanding payment of ransom in return for the access codes required to unlock files.
A remote access trojan program (or RAT), is a trojan horse capable of controlling a machine through commands issued by a remote attacker.
A type of malware that steals a system's resources (e.g., CPU cycles), such as a bitcoin miner.
A fake security product that demands money to clean phony infections.
A type of malware that hides its files or processes from normal methods of monitoring in order to conceal its presence and activities. Rootkits can operate at a number of levels, from the application level — simply replacing or adjusting the settings of system software to prevent the display of certain information — through hooking certain functions or inserting modules or drivers into the operating system kernel, to the deeper level of firmware or virtualization rootkits, which are activated before the operating system and thus even harder to detect while the system is running.
A type of malware used to capture images from the target systems screen, used for exfiltration and command and control.
Software that gathers information on a user's system without their knowledge and sends it to another party. Spyware is generally used to track activities for the purpose of delivering advertising.
Any malicious computer program which is used to hack into a computer by misleading users of its true intent.
A malicious computer program that replicates by reproducing itself or infecting other programs by modifying them.
A self-replicating, self-contained program that usually executes itself without user intervention.
Report label is an open vocabulary to describe the primary purpose or subject of a report. For example, a report that contains malware and indicators for that malware should have a report label of malware to capture that the malware is the primary purpose. Report labels are not mutually exclusive: a Report can be both a malware report and a tool report. Just because a report contains objects of a type does not mean that the report should include that label. If the objects are there to simply provide evidence or context for other objects, it is not necessary to include them in the label.
Report subject is a broad characterization of a threat across multiple facets.
Report subject is a characterization of one or more attack patterns and related information.
Report subject is a characterization of one or more campaigns and related information.
Report subject is a characterization of one or more identities and related information.
Report subject is a characterization of one or more indicators and related information.
Report subject is a characterization of one or more intrusion sets and related information.
Report subject is a characterization of one or more malware instances and related information.
Report subject is a characterization of observed data and related information.
Report subject is a characterization of one or more threat actors and related information.
Report subject is a characterization of one or more tools and related information.
Report subject is a characterization of one or more vulnerabilities and related information.
Threat actor label is an open vocabulary used to describe what type of threat actor the individual or group is. For example, some threat actors are competitors who try to steal information, while others are activists who act in support of a social or political cause. Actor labels are not mutually exclusive: a threat actor can be both a disgruntled insider and a spy [Casey 2007].
Highly motivated, potentially destructive supporter of a social or political cause (e.g., trade, labor, environment, etc.) that attempts to disrupt an organization's business model or damage their image.
This category includes actors sometimes referred to as anarchists, cyber vandals, extremists, and hacktivists.
An organization that competes in the same economic marketplace.
The goal of a competitor is to gain an advantage in business with respect to the rival organization it targets. It usually does this by copying intellectual property, trade secrets, acquisition strategies, or other technical or business data from a rival organization with the intention of using the data to bolster its own assets and market position.
An enterprise organized to conduct significant, large-scale criminal activity for profit.
Crime syndicates, also known as organized crime, are generally large, well-resourced groups that operate to create profit from all types of crime.
Individual who commits computer crimes, often for personal financial gain and often involves the theft of something valuable.
Intellectual property theft, extortion via ransomware, and physical destruction are common examples. A criminal as defined here refers to those acting individually or in very small or informal groups. For sophisticated organized criminal activity, see the crime syndicate descriptor.
An individual that tends to break into networks for the thrill or the challenge of doing so.
Hackers may use advanced skills or simple attack scripts they have downloaded.
A non-hostile insider who unintentionally exposes the organization to harm.
"Insider" in this context includes any person extended internal trust, such as regular employees, contractors, consultants, and temporary workers.
Current or former insiders who seek revengeful and harmful retaliation for perceived wrongs.
Disgruntled threat actors may have extensive knowledge that can be leveraged when conducting attacks and can take any number of actions including sabotage, violence, theft, fraud, espionage, or embarrassing individuals or the organization.
Entities who work for the government or military of a nation state or who work at their direction.
These actors typically have access to significant support, resources, training, and tools and are capable of designing and executing very sophisticated and effective Intrusion Sets and Campaigns.
Seeks to cause embarrassment and brand damage by exposing sensitive information in a manner designed to cause a public relations crisis.
A sensationalist may be an individual or small group of people motivated primarily by a need for notoriety. Unlike the activist, the sensationalist generally has no political goal, and is not using bad PR to influence the target to change its behavior or business practices.
Secretly collects sensitive information for use, dissemination, or sale.
Traditional spies (governmental and industrial) are part of a well-resourced intelligence organization and are capable of very sophisticated clandestine operations. However, insiders such as employees or consultants acting as spies can be just as effective and damaging, even when their activities are largely opportunistic and not part of an overall campaign.
Uses extreme violence to advance a social or political agenda as well as monetary crimes to support its activities.
In this context a terrorist refers to individuals who target noncombatants with violence to send a message of fear far beyond the actual events. They may act independently or as part of a terrorist organization.
Terrorist organizations must typically raise much of their operating budget through criminal activity, which often occurs online. Terrorists are also often adept at using and covertly manipulating social media for both recruitment and impact.
Threat actor role is an open vocabulary that is used to describe the different roles that a threat actor can play. For example, some threat actors author malware or operate botnets while other actors actually carry out attacks directly.
Threat actor roles are not mutually exclusive. For example, an actor can be both a financial backer for attacks and also direct attacks.
Threat actor executes attacks either on behalf of themselves or at the direction of someone else.
The threat actor who directs the activities, goals, and objectives of the malicious activities.
A threat actor acting by themselves.
Someone who designs the battle space.
The threat actor who provides and supports the attack infrastructure that is used to deliver the attack (botnet providers, cloud services, etc.).
The threat actor who authors malware or other malicious tools.
The threat actor who funds the malicious activities.
Threat actor sophistication vocabulary captures the skill level of a threat actor. It ranges from "none", which describes a complete novice, to "strategic", which describes an attacker who is able to influence supply chains to introduce vulnerabilities. This vocabulary is separate from resource level because an innovative, highly-skilled threat actor may have access to very few resources while a minimal-level actor might have the resources of an organized crime ring.
Can carry out random acts of disruption or destruction by running tools they do not understand. Actors in this category have average computer skills.
Can minimally use existing and frequently well known and easy-to-find techniques and programs or scripts to search for and exploit weaknesses in other computers. Commonly referred to as a script-kiddie.
These actors rely on others to develop the malicious tools, delivery mechanisms, and execution strategy and often do not fully understand the tool they are using or how they work. They also lack the ability to conduct their own reconnaissance and targeting research.
· have minimal knowledge of the tools.
Can proficiently use existing attack frameworks and toolkits to search for and exploit vulnerabilities in computers or systems. Actors in this category have computer skills equivalent to an IT professional and typically have a working knowledge of networks, operating systems, and possibly even defensive techniques and will typically exhibit some operational security.
These actors rely others to develop the malicious tools and delivery mechanisms, but are able to plan their own execution strategy. They are proficient in the tools they are using and how they work and can even make minimal modifications as needed.
· have proficient knowledge of the tools.
Can develop their own tools or scripts from publicly known vulnerabilities to target systems and users. Actors in this category are very adept at IT systems and have a background in software development along with a solid understanding of defensive techniques and operational security.
These actors rely on others to find and identify weaknesses and vulnerabilities in systems, but are able to create their own tools, delivery mechanisms, and execution strategies.
Can focus on the discovery and use of unknown malicious code, are is adept at installing user and kernel mode rootkits, frequently use data mining tools, target corporate executives and key users (government and industry) for the purpose of stealing personal and corporate data. Actors in this category are very adept at IT systems and software development and are experts with security systems, defensive techniques, attack methods, and operational security.
Typically criminal or state actors who are organized, highly technical, proficient, well-funded professionals working in teams to discover new vulnerabilities and develop exploits.
Demonstrates sophisticated capability. An innovator has the ability to create and script unique programs and codes targeting virtually any form of technology. At this level, this actor has a deep knowledge of networks, operating systems, programming languages, firmware, and infrastructure topologies and will demonstrate operational security when conducting his activities. Innovators are largely responsible for the discovery of 0-day vulnerabilities and the development of new attack techniques.
· create new and innovative attacks and toolkits.
State actors who create vulnerabilities through an active program to "influence" commercial products and services during design, development or manufacturing, or with the ability to impact products while in the supply chain to enable exploitation of networks and systems of interest.
· are responsible for APT-level attacks.
Tool labels describe the categories of tools that can be used to perform attacks.
Tools used to perform denial of service attacks or DDoS attacks, such as Low Orbit Ion Cannon (LOIC) and DHCPig.
Tools used to exploit software and systems, such as sqlmap and Metasploit.
Tools used to enumerate system and network information, e.g., NMAP.
Tools used to capture network traffic, such as Wireshark and Kismet.
Tools used to crack password databases or otherwise exploit/discover credentials, either locally or remotely, such as John the Ripper and NCrack.
Tools used to access machines remotely, such as VNC and Remote Desktop.
Tools used to scan systems and networks for vulnerabilities, e.g., Nessus.
There are two primary means to customize STIX: Custom Properties, and Custom Objects. Custom Properties provides a mechanism and requirements for adding properties not defined by this specification to existing STIX Objects. Custom Objects, on the other hand, provides a mechanism and requirements to create custom STIX Objects (objects not defined by this specification).
A consumer that receives a STIX document containing Custom Properties or Objects it does not understand MAY refuse to process the document or MAY ignore those properties or objects and continue processing the document.
Producers of STIX documents that contain Custom Properties or Objects should recognize that consumers may not understand them and may ignore them. Producers should define any Custom Properties and Objects they use, along with any rules for processing them, and make these definitions and rules accessible to any potential consumers. This specification does not specify a process for doing this.
There will be cases where certain information exchanges can be improved by adding properties that are neither specified nor reserved in this document; these properties are called Custom Properties. This section provides guidance and requirements for how producers can use Custom Properties and how consumers should interpret them in order to extend STIX in an interoperable manner.
· A STIX Object MAY have any number of Custom Properties.
· Custom Property names MUST be in ASCII and MUST only contain the characters a–z (lowercase ASCII), 0–9, and underscore (_).
· Custom Property names SHOULD start with "x_" followed by a source unique identifier (such as a domain name with dots replaced by underscores), an underscore and then the name. For example, x_example_com_customfield.
· Custom Property names MUST have a minimum length of 3 ASCII characters.
· Custom Property names MUST be no longer than 250 ASCII characters in length.
· Custom Property names that do not start with "x_" may be used in a future version of the specification for a different meaning. If compatibility with future versions of this specification is required, the "x_" prefix MUST be used.
· Custom Properties SHOULD only be used when there is no existing properties defined by the STIX specification that fulfils that need.
There will be cases where certain information exchanges can be improved by adding objects that are not specified nor reserved in this document; these objects are called Custom Objects. This section provides guidance and requirements for how producers can use Custom Objects and how consumers should interpret them in order to extend STIX in an interoperable manner.
· Producers MAY include any number of Custom Objects in STIX documents.
· Custom Objects MUST support the Common Properties as defined in section 3.1.
o The definitions of these properties are the same as those defined in Common Properties and therefore those properties MUST NOT be used to represent the custom properties in the object.
· The type property in a Custom Object MUST be in ASCII and MUST only contain the characters a–z (lowercase ASCII), 0–9, and hyphen (-).
· The type property MUST NOT contain a hyphen (-) character immediately following another hyphen (-) character.
· Custom Object names MUST have a minimum length of 3 ASCII characters.
· Custom Object names MUST be no longer than 250 ASCII characters in length.
· The value of the type property in a Custom Object SHOULD start with "x-" followed by a source unique identifier (like a domain name with dots replaced by dashes), a dash and then the name. For example, x-example-com-customobject.
· A Custom Object whose name is not prefixed with "x-" may be used in a future version of the specification with a different meaning. Therefore, if compatibility with future versions of this specification is required, the "x-" prefix MUST be used.
· The value of the id property in a Custom Object MUST use the same format as the identifier type, namely, [object-type]--[UUIDv4].
· Custom Objects SHOULD only be used when there is no existing STIX Object defined by the STIX specification that fulfils that need.
1. It MUST be able to create content encoded as JSON.
2. All required properties MUST be present in the created content.
3. All properties MUST conform to the data type and normative requirements for that property.
4. It MUST support at least one STIX Object per the Conformance section in STIX™ Version 2.0. Part 2: STIX Objects.
5. It MUST support all features listed in section 8.2, Mandatory Features.
6. It MAY support any features listed in section 8.3, Optional Features. Software supporting an optional feature MUST comply with the normative requirements of that feature.
1. It MUST support parsing all required properties for the content that it consumes.
2. It MUST support all features listed in section 8.2, Mandatory Features.
3. It MAY support any features listed in section 8.3, Optional Features. Software supporting an optional feature MUST comply with the normative requirements of that feature.
A STIX 2.0 Producer or STIX 2.0 Consumer MUST support versioning by following the normative requirements listed in section 3.4.
A STIX 2.0 Producer or STIX 2.0 Consumer MAY support "Object-Level Data Markings". Software claiming to support "Object-Level Data Markings" MUST follow the normative requirements listed in sections 4.1 and 4.2.
A STIX 2.0 Producer or STIX 2.0 Consumer MAY support "Granular Data Markings". Software claiming to support "Granular Data Markings" MUST follow the normative requirements listed in sections 4.1 and 4.3.
Christian Hunt, New Context Services, Inc.
John-Mark Gurney, New Context Services, Inc.
Owen Johnson, Blue Coat Systems, Inc.
Aubrey Merchant, Blue Coat Systems, Inc.
Xiaoyu Ge, Huawei Technologies Co., Ltd.
David Laurance, JPMorgan Chase Bank, N.A.
Daniel Riedel, New Context Services, Inc.
Andrew Storms, New Context Services, Inc.
Ted Julian, Resilient Systems, Inc..


text:
Glenn E. Wolgemuth (1947-2020)
by Clauser Funeral Home October 10, 2020 Updated October 13, 2020
Glenn E. Wolgemuth, 73, of Schaefferstown, passed away unexpectedly on Saturday, Oct. 10, 2020 at the Wellspan Good Samaritan Hospital. He was the husband of Bonita (Bonnie) Fittery Wolgemuth to whom he was married for 50 years.
He was born on Mar. 8, 1947, to the late Galen H. and June G. (Patches) Wolgemuth.
Glenn served as president of Sheridan Supply Company, Inc. in Newmanstown. He was a member of the St. Paul's United Church of Christ in Schaefferstown; Mt. Lebanon Lodge 226, Lebanon Council No. 27 Royal and Select Masons, Weible Royal Arch Chapter No. 197, Hermit Commandery No. 24 Knights Templar, Past Grand Tall Cedar of Quittapahilla/Forest No. 25 Tall Cedars of Lebanon, Quittie Woods, Inc.; Richland American Legion, Post 880; Heidelberg Lions Club; Mox Nix Investment Club, Poker Pals Group, and the former Lebanon Valley Corvette Club. He previously served as Chairman of the Lebanon County Republican Committee and was a member of the PA State Republican Committee, as well as several years as President of Schaefferstown Water Company/Fountain Park; served as a Heidelberg Township Supervisor and on the Heidelberg Township Planning Committee and currently as a Heidelberg Township Auditor.
He was a graduate of Elco High School, Class of 1965, and served in the U.S. Army from 1968-1972. He enjoyed many hobbies over the years, including flying his Cessna 150, riding motorcycle, and driving his pride and joy, a 1964 DNEPRK-750M, around the Schaefferstown area with his dog in the sidecar. Glenn, known to some as Crusher, lived a full life of tinkering, building, and creating. Not a moment of rest in him, he could be found welding a project, perfecting a motorcycle, or refurbishing an antique. A man of few words, Glenn will be remembered for expressing his satisfaction in "buzzes." A mentor, a leader, a dedicated father, grandfather, and friend, Glenn will be sorely missed.
Surviving, in addition to his wife, are children, Shelly Fessler and husband Steve; Jamie Wolgemuth and wife Jen; Jared Wolgemuth and wife Jena; grandchildren, Alex Derr, Ethan Derr, Vanessa Wolgemuth, Cameron Wolgemuth, and Jack Wolgemuth; sisters, Marilyn Gillespie and husband Charles; Cindy Hall-Baker; brothers, John Wolgemuth, and Loren Wolgemuth and wife Julie. He was preceded in death by brother, Jay Wolgemuth, and sister, Gail Wolgemuth.
Graveside service to be held at the convenience of the family with a "Celebration of Life" forthcoming. In lieu of flowers, donations can be made to: St. Paul's U.C.C., P.O. Box 375, Schaefferstown, PA 17088, or the American Heart Association, Lebanon Division, 610 Community Way, Lancaster, PA 17603. Please mail condolences to: Wolgemuth, P. O. Box 300, Schaefferstown, PA 17088. Clauser Funeral Home, Inc. is handling his arrangements. www.clauserfh.com