text:
OPSEU gives thumbs down to Ford's attempt to fix cannabis debacle
The Ford government's latest reset of its disastrous decision to privatize cannabis sales is bound to make an already bad situation worse, says OPSEU President Warren (Smokey) Thomas.
"What will it take for the government to understand that cannabis retail stores need to be operated by trained professionals?" asked Thomas.
Thomas can't believe the Ford government is set to move to an "open allocation" system for issuing retail cannabis licenses as early as January that could result in over 1,000 outlets across Ontario.
"I can't figure out why the Conservatives think it makes sense to continue on with this privatization disaster," said Thomas. "We need a Responsible Plan, the kind of plan the previous government had that would have put cannabis sales in the hands of the LCBO.
"Polls have shown us that Ontarians are 11 times more likely to trust the LCBO than private retailers when it comes to keeping cannabis out of kids' hands," Thomas added.
"This is a matter of public safety. LCBO stores have trained professionals who have the training and experience to handle sales of controlled substances."
Over a year ago when the discussion around cannabis retail stores began, the Ford government made a number of promises – promises they are now breaking, says Thomas.
"They promised a tightly regulated system. What does this new plan involve? It involves flooding the market. How is that responsible? The second promise was to keep our kids safe. This doesn't keep our kids safe."
"Our members who operate LCBO stores are experts in responsible sales," he adds. "They keep our kids and our communities safe because they are trained and qualified. They take social responsibility seriously."
It's time for Ford to give up trying to find solutions for a problem that doesn't exist, says OPSEU First Vice President/Treasurer, Eduardo (Eddy) Almeida.
"The solution has been there in front of them all along," says Almeida. "How many failed attempts and half-baked ideas are they going to try?"
"First Mr. Ford hits us with a crazy lottery scheme that resulted in only a handful of stores operated by people as random as the process that selected them and now he just wants to open this up as a free-for-all? We need a clear and thoughtful plan, and the LCBO is the solution."
SOURCE Ontario Public Service Employees Union (OPSEU)
Leave a Reply
Leave a Reply
'Potently Canadian' Cannabis Brand, CANACA, Launches 'Let 'Er Rip' Campaign
TORONTO, Sept. 29, 2023 (GLOBE NEWSWIRE) — Tilray Brands, Inc. ("Tilray" or the "Company") (Nasdaq: TLRY; TSX: TLRY), a leading global cannabis and consumer packaged goods company, today announced the launch of its expanded product lineup by its quintessentially Canadian cannabis lifestyle brand, CANACA. Introducing its new 'Let 'Er Rip' Campaign, a curated collection of products crafted to elevate intensity while offering flavourful and aromatic consumption experiences. As part of the new campaign, CANACA highlights two product lines, unveiling exciting new offerings just in time for fall, including additional whole flower and Crumble Cones™ pre-rolls.
"We are excited to launch this campaign, which demonstrates CANACA's redefined brand narrative, emphasizing the innovative enhancements we've incorporated into our processes, thereby elevating our product quality," said Michelle Morin, Senior Brand Manager at Tilray Brands. "Innovation is at the core of the brand's evolution; it drives us to craft cannabis products that not only meet but exceed consumer expectations."
CANACA delivers this experience by placing a renewed emphasis on meticulous production. The refined growing and processing techniques, including hang drying, hand trimming, and a 14-day curing period, are distinctly reflected in the quality of our whole flower products. Moreover, our innovative technologies, such as the proprietary process for creating the full spectrum extract, deliver extra smooth smoke in our Crumble Cones.
In select stores, consumers will have the opportunity to explore new educational resources, delving into how each format is offered by CANACA. Immersing themselves in the vibrant visual assets encapsulating the feeling delivered by CANACA products: Let 'Er Rip!
CANACA's high-quality whole flower includes:
- Afghaniskunk: For those that love a good skunk strain that's sour yet sweet, this strain is a cross between Afghan #1 and Skunk, only available in 7g in Ontario and 28g flower in Alberta, Manitoba, and Saskatchewan.
- Ghost Gelato: Nothing like Gelato #9 and Ghost Train Haze to bring you the ultimate sour, fruity and citrus notes to enjoy, available in 7g and 28g flower, along with 14 x 0.35g pre-roll multi-packs.
- Headbanger: One of CANACA's latest new Fall releases, headbanger brings a trifecta of goodness, featuring fruit, earth, and gas aromas, thanks to its blend of Biker Kush and Sour Diesel. Available in 7g in Ontario and 28g flower in Alberta, Manitoba, and Saskatchewan.
- Alien Guy: A CANACA classic – a blend of Jean Guy and Alien Dawg bringing you citrus, lemon and pine aromas, embracing classically Canadian notes, available 7g and 28g flower, and 14 x 0.35g pre-roll multi-packs.
With boosted potency and smoothness, CANACA also introduces two additional Crumble Cones offerings:
- Grandpa's Stash: Grandpa's Stash Crumble Cones combine ground Grandpa's Stash sativa flower with butane hash oil (BHO) crumble to create infused pre-rolls that embrace sweet, spicy and dank aromas from the dominant caryophyllene, humulene and limonene terpenes from this Super Skunk x OG Kush x Afghan Kush cross with an amped-up BHO infusion. Grab Grandpa's Stash Crumble Cones in a 3 x 0.5g pack.
- Ghost Gelato: Ghost Gelato Crumbles Cones combines Ghost Gelato indica flower with butane hash oil (BHO) crumble to create infused pre-rolls, achieving higher THC. Experience the power of these pre-rolls with citrus, sour, and earthy aromas from the dominant limonene, caryophyllene, and myrcene terpenes, derived from a cross of Ghost Train Haze x Gelato #9 and amped-up BHO infusion. Grab Ghost Gelato Crumble Cones in a 1 x 1g pack.
CANACA's 'Let Er' Rip' campaign signifies a new chapter, showcasing products meticulously crafted for enhanced intensity and focusing on potency and aroma. This reinforces our commitment to offering 'true north strong' products, introducing additional potent options for consumers.
Our products are available across select regions and retailers throughout Canada.
About CANACA
CANACA is a proudly Canadian brand that indulges your unapologetic love for Canada and cannabis. We're all about elevated adventures and expanding your horizons. The ones where you're enjoying the journey, not just the destination. We're passionate about crafting cannabis that's consistent, reliable, and full of character — just like the people we serve.
Our products are curated and designed to serve the unique and ever-evolving cannabis needs and wants of Canadians. We're proud of our work and the people and places that produce our products. That's why CANACA is grown, produced, and packaged in small-town Canada and always will be. We're potently Canadian, and dang proud of it.
For more information on CANACA, follow @CANACAyourbud on Instagram.
About Tilray Brands
Tilray Brands, Inc. (Nasdaq: TLRY and TSX: TLRY) is a leading global cannabis-lifestyle and consumer packaged goods company with operations in Canada, the United States, Europe, Australia, and Latin America that is changing people's lives for the better – one person at a time – by inspiring and empowering the worldwide community to live their very best life by providing them with products that meet the needs of their mind, body, and soul and invoke a sense of wellbeing. Tilray's mission is to be the trusted partner for its patients and consumers by providing them with a cultivated experience and health and wellbeing through high-quality, differentiated brands and innovative products. A pioneer in cannabis research, cultivation, and distribution, Tilray's unprecedented production platform supports over 20 brands in over 20 countries, including comprehensive cannabis offerings, hemp-based foods, and alcoholic beverages.
For more information on Tilray Brands, visit www.Tilray.com and follow @Tilray
Forward-Looking Statements
Certain statements in this communication that are not historical facts constitute forward-looking information or forward-looking statements (together, "forward-looking statements") under Canadian securities laws and within the meaning of Section 27A of the Securities Act of 1933, as amended, and Section 21E of the Securities Exchange Act of 1934, as amended, that are intended to be subject to the "safe harbor" created by those sections and other applicable laws. Forward-looking statements can be identified by words such as "forecast," "future," "should," "could," "enable," "potential," "contemplate," "believe," "anticipate," "estimate," "plan," "expect," "intend," "may," "project," "will," "would" and the negative of these terms or similar expressions, although not all forward-looking statements contain these identifying words. Certain material factors, estimates, goals, projections, or assumptions were used in drawing the conclusions contained in the forward-looking statements throughout this communication. Forward-looking statements include statements regarding our intentions, beliefs, projections, outlook, analyses, or current expectations concerning, among other things, the Company's ability to commercialize new and innovative products worldwide. Many factors could cause actual results, performance, or achievement to be materially different from any forward-looking statements, and other risks and uncertainties not presently known to the Company or that the Company deems immaterial could also cause actual results or events to differ materially from those expressed in the forward-looking statements contained herein. For a more detailed discussion of these risks and other factors, see the most recently filed annual information form of Tilray and the Annual Report on Form 10-K (and other periodic reports filed with the SEC) of Tilray made with the SEC and available on EDGAR. The forward-looking statements included in this communication are made as of the date of this communication and the Company does not undertake any obligation to publicly update such forward-looking statements to reflect new information, subsequent events, or otherwise unless required by applicable securities laws.
Tilray Brands
Kaitlin Macapagal
Raphael Gross
Hemp, Inc. Reports: Growing Legalization of Industrial Hemp Driving Global Demand for Hemp
LAS VEGAS, NV, Sept. 28, 2023 (GLOBE NEWSWIRE) — via NewMediaWire – Hemp, Inc. (OTC PINK: HEMP) is perfectly positioned at the forefront of the industrial hemp industry as demand increases and opportunities abound. The recent release of a comprehensive research report, Global Industrial Hemp Market (2023-2031), says the global industrial hemp market is forecast to grow to $134.6 billion by 2030. The report covers trends, investments, tech advancements, and some of the major players in the industry. Of particular interest in this report are the factors that are influencing the market because these are the things creating exponential growth opportunities for industry businesses. For example, did you know hemp seeds are known as a "complete" protein source? By complete, we mean the nine essential amino acids your body typically needs on a daily basis.
These amino acids are essential because they can only be derived from your diet. Let's delve a little deeper into what those essential amino acids are. They are histidine, isoleucine, leucine, lysine, methionine, phenylalanine, threonine, tryptophan, and valine. Quite a mouthful but quite essential. In fact, in the plant world, there are only five other plants considered a complete protein source (amaranth, buckwheat, chia seeds, quinoa, and soy). More and more people are becoming aware of such benefits and there's a growing consumer demand for a nutrition-rich diet.
As one of the most rapidly growing plants on the planet, hemp is used to make a variety of products. It can be shifted into rope, paper, textiles, clothing, disposable polymers, paint, insulation, food, and animal feed. (Source) Hemp, Inc. discovered its grounded kenaf hemp blend is the perfect substrate to grow healthy and/or medicinal mushrooms and has the capability to make and/or provide the raw materials to produce hemp-based products such as hempcrete, horse bedding, hemp bio-plastics, and more. With the "growing legalization of industrial hemp farming around the world, the demand for industrial hemp has been exponential. There's been a rapid expansion of various R&D activities that will benefit the market and the beneficial properties of hemp seed oil and hemp seeds are also significantly influencing the industrial hemp market." (Source)
With over 14 years of experience in hemp cultivation and processing, Hemp, Inc. plays a pivotal role in the industrial hemp industry. The company's product line includes CBD, CBDA, CBG, CBGA, and CBN, all derived from hemp and known for their therapeutic properties. Hemp, Inc. distinguishes itself by using pharmaceutical-grade beta-cyclodextrin in combination with cannabinoids for rapid absorption and efficacy. Notably, their CBD/CBG coffee enhancer is highly potent, rapidly absorbed, and competitively priced, offering consumers a premium coffee experience.
Needless to say, Hemp, Inc. continues to have a strong foothold in the market with an invaluable roster of manufacturers and vendors across the country and abroad to see meteoric growth curves on a domestic and international scale and its e-portal (www.hempinc.com) to its CBD products is primed and poised to capture a large share of the marketplace on a global scale.
The Company's superb lineup of CBD/CBG/CBN products includes a CBD-CBG Topical Pain Relief Roll-on (THC-free with 1,460mg of CBD and 630mg of CBG totaling 2,090mg of cannabinoids in 5ml), CBD/CBG Natural Coffee Enhancers, CBD/CBG Tinctures, and, CBDa/CBGa/CBD/CBG/CBN Capsules.
Hemp has and will continue to play a vital role in maintaining good health and well-being. Read on for how Hemp, Inc.'s current product line is a step above the rest.
About Hemp, Inc.'s Current Product Line
The product line contains CBD, CBDA, CBG, CBGA, and CBN (non-psychoactive compounds found in cannabis plants). These are active ingredients in cannabis that are derived from the hemp plant, which is widely known for pain relief, relaxation, and anxiety relief. A recipe is only as good as its ingredients and how those ingredients are blended. Hemp, Inc. is the only company in America that uses pharmaceutical-grade beta-cyclodextrin (a carbohydrate used during the manufacturing process) which is combined with all the cannabinoids for rapid absorption and uptake. The Company's CBD, CBDA, CBG, CBGA, and CBN product lines are highly potent therapeutic doses that have received rave reviews.
Hemp, Inc. has also pushed the boundaries with its CBD/CBG coffee enhancer. This powerhouse product is super potent, absorbs rapidly in coffee, and is 4 times more potent (at a fraction of the price) than other hemp-derived coffee enhancers currently on the market. Its high-quality ingredient combination offers 30 servings per bottle and contains a total of 10,000mg of cannabinoids (7,500mg CBD and 2,500mg CBG) in an MCT oil base. Per serving, that's 250mg CBD and 83mg CBG remarkably mixed in a wonderfully rich cup of coffee.
The CBD/CBG coffee enhancer comes in plain (natural) and vanilla flavors. The plain (natural) coffee enhancer is available now and the vanilla flavor will be available by the end of this month. A single container (7-day supply) retails for $27.95 and a bottle (30-day supply) retails for $99.95. Wholesale bulk orders are single-use packages, available through select restaurants.
For more information on Hemp, Inc.'s products, click here. Catch up on Hemp, Inc.'s latest news below.
Hemp, Inc. Reports: Global Natural Fiber Composites (Hemp, Kenaf, and Flax) Market Set to Reach $424 Million by 2028
Hemp, Inc. Profiled as Key Player in Latest Industrial Hemp Industry Report on Emerging Trends, Growth, and Future Scope by 2027
Hemp, Inc. Reports Higher Education Aims to Harness Hemp's Full Potential From Field to Fabric
Hemp, Inc. Reports: Hemp Seed and Hemp Fiber Set to Flourish on a Global Scale
Hemp, Inc. Reports: Hemp-Based Product Sales Expected to Reach $16.2 Billion by 2033
Hemp, Inc. Reports: Hemp Recognized as Specialty Crop with US Department of Agriculture
Significant Increase in Revenue Proving 2023 to be a Banner Year for Hemp, Inc.
Hemp, Inc. Reports: Industrial Hemp Act 2023
New Look, New Feel for Hemp, Inc.'s Hempinc.com
Hemp Inc.'s Year-to-Date Sales Increase 315% Over Last Year
Hemp Inc. Reports Third Quarter Results and Removal of "Yield" Sign
Hemp Inc. Reveals Stunning Results of its Hemp Research
Hempcrete Approved for U.S. Residential Construction
Hemp Inc. See Significant Increase in Revenue Over the Last 3 Quarters
Hemp, Inc. Offers CBD-CBG Topical Pain Relief Roll-On
Hemp, Inc.'s Chief Visionary Consultant Bruce Perlowin Brings Opportunity to Hemp, Inc. (August 8, 2022)
Hemp Inc.'s CBDA and CBGA Products on Sale Now (July 19, 2022)
Hemp Inc.'s Chief Visionary Consultant Bruce Perlowin talks with Stock Day podcast about Hemp Inc.'s super potent line of CBD/CBG/CBN Products (July 7, 2022)
Healthy Products for Healthy Living: A Look into Hemp, Inc.'s Pure, Premium, and Potent CBD and Wellness Products (June 16, 2022)
Hemp, Inc. Releases New High Potency CBD/CBG Vanilla Flavored Coffee Enhancer (June 9, 2022)
Hemp, Inc.'s King of Hemp CBD-CBG-CBN Natural Sleep Aid Capsules in Stock and On Sale (May 26, 2022)
King of Hemp Natural and Vanilla-Flavored CBD/CBG "Super" Tinctures Now in Stock (May 12, 2022)
About Hemp, Inc.
With more than 14 years of experience in growing and processing hemp in North America, Hemp, Inc. has an established network of industry professionals in every segment of the industrial hemp industry. Its mission of providing green solutions that help make the world a better place continues to flourish as the company advances an ever-growing portfolio of revenue and value-generating synergistic businesses. Hemp may be the salvation in retooling America for greener, more sustainable domestic manufacturing.
The Company will continue to keep its shareholders up to date on all pertinent material events, product releases, production plans, and inventory availability. Those interested in distributing on a large-scale basis should email firstname.lastname@example.com or call 877-436-7564 for more information. The entire product line includes tinctures, gummies, capsules, and edibles in a variety of sizes, potencies, flavors, and formulas with a future focus on healthy foods for healthy living.
Forward-Looking Statements
This press release may contain certain forward-looking statements and information, as defined within the meaning of Section 27A of the Securities Act of 1933 and Section 21E of the Securities Exchange Act of 1934, and is subject to the Safe Harbor created by those sections. The Securities and Exchange Commission (SEC) requires issuers to provide "adequate current information". Financials for Hemp, Inc. are listed on the OTC Exchange. More information can also be found on the Hemp, Inc. website by visiting www.hempinc.com/financial-disclosures/. The material contains statements about expected future events and/or financial results that are forward-looking in nature and subject to risks and uncertainties. Such forward-looking statements involve risks and uncertainties.
Hemp, Inc.
Investor Relations
(720) 220-0037
Astrotech Reports Fiscal Year 2023 Financial Results
AUSTIN, Texas, Sept. 28, 2023 (GLOBE NEWSWIRE) — Astrotech Corporation (Nasdaq: ASTC) (the "Company" or "Astrotech") reported its financial results for the fiscal year ended June 30, 2023.
Financial Highlights & Fiscal Year Developments
- Astrotech's consolidated balance sheet remains strong with $42.1 million in cash and cash equivalents and liquid investments which is anticipated to support our research and development, organic growth, and potential acquisition targets.
- Gross margin increased to 41% for the year compared to 22% in the prior period, due to a higher proportion of recurring revenue.
- We appointed Bob McFarland to the Board of Directors to bring his domestic and international executive management and sales experience, as well as his experience working with and for the federal government.
- We appointed Thomas B. Pickens III to the role of Chief Technology Officer. He has consistently demonstrated his proficiency in identifying new applications that can "profit" from our Astrotech Mass Spectrometer Technology™ (the "AMS Technology") and is key in the design of innovative sample collection, software user interface, and quantitation techniques. Mr. Pickens is also integral in creating value by identifying and integrating OEM suppliers of certain sample collection and chromatography technologies.
- Our 1st Detect subsidiary's commercial sales of the ECAC-certified TRACER 1000™ explosive trace detector (ETD), consumables and recurring maintenance services has continued leading to $750 thousand in total revenue during the fiscal year ended June 30, 2023. Additionally, 1st Detect has been successful in securing an order for 17 Tracer 1000 units to a Romanian based security and telecommunications company with the majority of these units being delivered in early fiscal year 2024.
- Our AgLAB subsidiary released results from the ongoing field trials of the AgLAB Maximum Value Process™ solution (AgLAB MVP). AgLAB which uses the Company's proprietary AgLAB 1000-D2™ mass spectrometer has been proven to improve distillation oil yields and bottom-line profits for hemp and cannabis producers. During our field trials, we were able to improve ending-weight yields by an average of 30%.
- Our BreathTech subsidiary continues to collect breath samples from both COVID-19 positive and negative patients as part of the ongoing development of the library for the BreathTest-1000™ lung disease screening instrument. The BreathTest-1000 is a breath analysis tool designed to screen for volatile organic compound metabolites found in a person's breath that could indicate they may have a bacterial or viral infection. Testing is being done following FDA required regulations.
- On December 5, 2022, the Company effected a reverse stock split primarily intended to bring the Company into compliance with the minimum bid price requirements for maintaining its listing on The Nasdaq Stock Market LLC. On December 19, 2022, the Company received written notice from the Listing Qualifications Department of Nasdaq stating that the Company had regained compliance with the minimum bid price requirement of $1.00 per share for continued listing on The Nasdaq Capital Market. Numbers presented in the financial statements presented have been adjusted to reflect the reverse stock split.
"The Company's gross profit grew in fiscal year 2023 as recurring revenue related to our TRACER 1000 was a larger proportion of our sales. After having lost traction with passenger airport sales during the pandemic, the Company is very excited about our most recent 17-unit order to Romania. These sales and our recurring revenue should result in an increase in our topline revenue during the next fiscal year," stated Thomas B. Pickens, III, Astrotech's Chairman, Chief Executive Officer and Chief Technology Officer.
During fiscal year 2023 we continued to develop and enhance our AMS Technology. This not only benefits our existing platforms but also provides additional versatility for the future.
"In addition, our AgLAB 1000-D2 field trials with potential customers have proven that the AgLAB MVP solution is an effective tool to improve potency and yields for any distiller of hemp or cannabis. We believe this technology has the ability to directly increase processors' bottom line. We are actively demonstrating the AgLAB MVP solution to several potential customers and are hopeful to secure our first deployments of the AgLAB 1000-D2" stated Thomas B. Pickens, III.
About Astrotech Corporation
Astrotech (Nasdaq: ASTC) is a mass spectrometry company that launches, manages, and commercializes scalable companies based on its innovative core technology through its wholly-owned subsidiaries. 1st Detect develops, manufactures, and sells trace detectors for use in the security and detection market. AgLAB develops and sells chemical analyzers for use in the agriculture market. BreathTech is developing a breath analysis tool to screen for volatile organic compounds that could indicate bodily infections and critical conditions. Astrotech is headquartered in Austin, Texas. For information, please visit www.astrotechcorp.com.
About the AgLAB 1000™ and the BreathTest-1000™
This press release contains information about our new products under development, AgLAB 1000 and BreathTest-1000. Product development involves a high degree of risk and uncertainty, and there can be no assurance that our new products will be successfully developed, achieve their intended benefits, receive full market authorization, or be commercially successful. In addition, FDA approval will be required to market BreathTest-1000 in the United States. Obtaining FDA approval is a complex and lengthy process, and there can be no assurance that FDA approval for BreathTest-1000 will be granted on a timely basis or at all.
Forward-Looking Statements
This press release contains forward-looking statements that are made pursuant to the Safe Harbor provisions of the Private Securities Litigation Reform Act of 1995. Such forward-looking statements are subject to risks, trends, and uncertainties that could cause actual results to be materially different from the forward-looking statement. These factors include, but are not limited to, the adverse impact of recent inflationary pressures, including significant increases in fuel costs, global economic conditions and events related to these conditions, including the ongoing war in Ukraine and the COVID-19 pandemic, the Company's use of proceeds from the common stock offerings, whether we can successfully complete the development of our new products and proprietary technologies, whether we can obtain the FDA and other regulatory approvals required to market our products under development in the United States or abroad, whether the market will accept our products and services and whether we are successful in identifying, completing and integrating acquisitions, as well as other risk factors and business considerations described in the Company's Securities and Exchange Commission filings including the Company's most recent Annual Report on Form 10-K. Any forward-looking statements in this document should be evaluated in light of these important risk factors. Although the Company believes the expectations reflected in its forward-looking statements are reasonable and are based on reasonable assumptions, no assurance can be given that these assumptions are accurate or that any of these expectations will be achieved (in full or at all) or will prove to have been correct. Moreover, such statements are subject to a number of assumptions, risks and uncertainties, many of which are beyond the control of the Company, which may cause actual results to differ materially from those implied or expressed by the forward-looking statements. In addition, any forward-looking statements included in this press release represent the Company's views only as of the date of its publication and should not be relied upon as representing its views as of any subsequent date. The Company assumes no obligation to correct or update these forward-looking statements, whether as a result of new information, future events or otherwise, except as required by applicable law.
Company Contact: Jaime Hinojosa, Chief Financial Officer, Astrotech Corporation, (512) 485-9530.
Tables follow
|Consolidated Statements of Operations and Comprehensive Loss
|(In thousands, except per share data)
|Years Ended
|June 30,
|Cost of revenue
|Gross profit
|Operating expenses:
|Selling, general and administrative
|Research and development
|Total operating expenses
|Loss from operations
|Other income and expense, net
|Loss from operations before income taxes
|Income tax benefit
|Net loss
|Weighted average common shares outstanding:
|Basic and diluted
|Basic and diluted net loss per common share:
|Net loss per common share
|Other comprehensive loss, net of tax:
|Net loss
|Available-for-sale securities
|Net unrealized losses, net of zero tax expense
|Total comprehensive loss
|Consolidated Balance Sheets
|(In thousands, except share and per share data)
|June 30,
|Current assets
|Cash and cash equivalents
|Short-term investments
|Accounts receivable
|Contract Asset
|Inventory, net:
|Raw materials
|Finished goods
|Income tax receivable
|Prepaid expenses and other current assets
|Total current assets
|Property and equipment, net
|Operating lease right-of-use assets, net
|Other assets, net
|Total assets
|Liabilities and stockholders' equity
|Current liabilities
|Accounts payable
|Payroll related accruals
|Accrued expenses and other liabilities
|Income tax payable
|Term note payable – related party
|Lease liabilities, current
|Total current liabilities
|Lease liabilities, net of current portion
|Total liabilities
|Commitments and contingencies
|Stockholders' equity
|Convertible preferred stock, $0.001 par value, 2,500,000 shares authorized; 280,898 shares of Series D issued and outstanding at June 30, 2023 and 2022, respectively
|Common stock, $0.001 par value, 250,000,000 shares authorized at June 30, 2023 and 2022 respectively; 1,692,045 and 1,685,595 shares issued and outstanding at June 30, 2023 and 2022, respectively; 1,681,729 and 1,685,595 outstanding at June 30, 2023 and 2022, respectively
|Treasury shares, 10,316 shares and no shares at June 30, 2023 and 2022, respectively
|Additional paid-in capital
|Accumulated deficit
|Accumulated other comprehensive loss
|Total stockholders' equity
|Total liabilities and stockholders' equity
Latest news
- Global Cannabis Market Projected To Reach $444 Billion By 2030 As Consumption and Demand Skyrockets
- 'Potently Canadian' Cannabis Brand, CANACA, Launches 'Let 'Er Rip' Campaign
- Hemp, Inc. Reports: Growing Legalization of Industrial Hemp Driving Global Demand for Hemp
- Astrotech Reports Fiscal Year 2023 Financial Results
- Canopy Growth Announces Results of Annual General and Special Meeting of Shareholders
- Global Exosomes Market Size to Reach USD 3.08 Billion in 2032 | Emergen Research
- Global CBD Oil Market to Reach US$ 5.98 billion by 2033, growing at a CAGR of 31% | Future Market Insights, Inc.
- New to The Street Announces its Five Corporate Interviews, airings on Newsmax and FOX Business Network
- CBD Skin Care Market Size is projected to reach USD 6466.43 million by 2030, growing at a CAGR of 32.15%: Straits Research
- Legal Cannabis Commercialization Bolsters Vacuum Oven Demand; Essential Role in Processing Extracts and Enhancing Safety Recognized
- Endexx Announces Amended Consolidated 10-Q/A: Quarterly Report for The Quarter Ending March 31, 2023, Increasing Year-Over-Year 1013%
- IM Cannabis Announces CFO Departure
- New Report Reveals Pre-Rolls Emerge As The Second-Largest Product Category In Canada, Poised to Overtake Flower as the Leading Category
- Cannabidiol (CBD) Market Size ($ 15978.16 Billion by 2030 at CAGR of 18.36% CAGR) – which is Booming Strong Growth in the Globe till 2030
- Hemp, Inc.'s Creative Visionary Consultant, Bruce Perlowin, to be Interviewed Live on the Quantum Energy, Health, and Information Call Today
Trending on Grassnews
Cannabis2 weeks ago
Hemp, Inc.'s Creative Visionary Consultant, Bruce Perlowin, to be Interviewed Live on the Quantum Energy, Health, and Information Call Today
Cannabis2 weeks ago
New Report Reveals Pre-Rolls Emerge As The Second-Largest Product Category In Canada, Poised to Overtake Flower as the Leading Category
Cannabis2 weeks ago
IM Cannabis Announces CFO Departure
Cannabis2 weeks ago
Cannabidiol (CBD) Market Size ($ 15978.16 Billion by 2030 at CAGR of 18.36% CAGR) – which is Booming Strong Growth in the Globe till 2030
Cannabis2 weeks ago
Endexx Announces Amended Consolidated 10-Q/A: Quarterly Report for The Quarter Ending March 31, 2023, Increasing Year-Over-Year 1013%
Cannabis2 weeks ago
Legal Cannabis Commercialization Bolsters Vacuum Oven Demand; Essential Role in Processing Extracts and Enhancing Safety Recognized
Cannabis2 weeks ago
CBD Skin Care Market Size is projected to reach USD 6466.43 million by 2030, growing at a CAGR of 32.15%: Straits Research
Cannabis1 week ago
New to The Street Announces its Five Corporate Interviews, airings on Newsmax and FOX Business Network


text:
In this guide:
Executive Summary
This guide is intended to help you achieve your security compliance objectives using Parasoft's deep code analysis and advanced development analytics technologies. Parasoft code analysis tools secure and harden your code, while Parasoft analytics monitor and track progress toward security compliance goals. Parasoft also provides reporting mechanisms for demonstrating compliance during an audit.
The primary audience for this guide is the person or people responsible for configuring dev/test processes in your organization. It provides context, rationale, and configuration information for Parasoft's solution that helps you bake security compliance into your development process and implement a secure-by-design strategy.
Parasoft tools can analyze code against any set of programming guidelines, but the full security compliance solution supports the following industry standards and collections of guidelines out of the box:
- CWE Top 25 Most Dangerous Software Errors
- CWE on the Cusp
- OWASP Top 10
Each organization has different security requirements and environments. This guide is intended to help you set up and execute the security solution under the following scenario:
- Single compliance standard
- Single language
You can extend the basic process to other scenarios, including:
- Multiple languages and a single standard (project-based implementation)
- Multiple standards and a single language (e.g., OWASP + PCI)
- Combined quality with security
We recognize that each organization is at a different point in their security compliance initiative. You may be using this guide in your organization, for instance, while building the dev/test infrastructure, while others are much further along in their development journey. The Prerequisites section describes assumptions we make in this guide regarding the state of your dev/test infrastructure deployment.
This document guides you through the following security compliance implementation steps:
- Initial Set Up
- Define the Compliance Workflow
- Define Compliance Policy
- Choose and Adapt a Test Configuration
- Implement Your Compliance Strategy
- Monitor and Audit Compliance with Your Policy
- Advanced Configuration and Strategies
You should also review the Glossary of Terms section for clarity on terminology used in this guide.
Refer to the Appendix section for specific versions of Parasoft products that support security compliance features and functionality. The appendix also includes the supported development languages and system integrations referenced in this guide.
Parasoft Products
We assume that you are familiar with Parasoft technologies and have already deployed and licensed the following products:
- Desktop instance(s) of either Parasoft C/C++test, dotTEST, and/or Jtest
- Server instance of either Parasoft C/C++test, dotTEST, and/or Jtest
- Parasoft Findings Plug-in for CI tools (optional)
- Parasoft DTP
- Parasoft DTP Security Bundle
We assume that you will be using the following common systems and tools:
- A supported integrated development environment (IDE) for each team member using desktop instances of Parasoft code analysis tools (e.g., Eclipse, IntelliJ, VisualStudio). Integration with an IDE is optional but recommended.
- A supported source control management (SCM) system (e.g., git, Subversion).
- A supported continuous integration (CI) tool (e.g., Jenkins).
- A supported build system (e.g., Gradle, Maven, Ant, Bazel, Make, etc.). Integration with a build system is only required for automation with Jtest.
Supported Languages
Refer to the Appendix section for a full list of supported languages.
Initial Set Up
Prepare your dev/test environment by implementing the following components:
Integration with Your Build Tool
Parasoft tools include a command line interface that enable you to programmatically execute analysis and tests, but you can use the plug-ins shipped with your tool to integrate with your build system. The plug-ins enable the build system to execute code analysis when the build tool runs.
Building with Jtest
Parasoft Jtest must be integrated into one of the following supported build systems to automate analysis and run tests:
You can configure specific aspects of the analysis, such as which test configuration to execute, in the .properties file, in the build file, or both.
Building with dotTEST
Parasoft dotTEST supports integration with MSBuild and NAnt, but a build system is not required to automate analysis. Although build system integration eases automation, you can use a script to launch dotTEST with a specific .properties file and command line switches to configure code analysis execution.
Building with C/C++test
A variety of build systems are available for C and C++ development, including Make, CMake, Bazel, Bitbake, custom scripts, etc. Parasoft provides flexible ways to integrate with both common and custom build systems.
- Running Static Analysis (C/C++test Standard)
- Creating a Project Using an Existing Build System (C/C++test Professional for Eclipse)
- Creating a Project Using an Existing Build System (C/C++test Professional for Visual Studio)
C/C++test does, however, integrate with MSBuild and make-based build tools to collect code coverage.
Integration with CI
Parasoft tools include a command line interface that enables you to programmatically execute analysis and tests, but you can use the Parasoft Findings plug-ins to integrate with your CI process. The plug-ins allow your continuous integration system to consume the analysis results from Parasoft tools, which enables you to accept or reject the build. Additionally, the plug-ins provide visualizations of test execution and code analysis results directly in the CI interface.
The plug-ins are available for Bamboo, Jenkins, TeamCity, and Azure DevOps (formerly Visual Studio Team Services) CI systems. You can download the code for each project from Parasoft's GitHub page.
Refer to the Parasoft Findings documentation for details on installation, configuration, and usage.
Installing and Deploying the Parasoft Security Bundle
The Parasoft Security Bundle is a package of tools for your DTP infrastructure that provide visibility into your security compliance efforts. The Security Bundle contains configurations that align the findings sent to DTP with security guidelines. It also includes specialized reporting mechanisms that enable you to demonstrate compliance with guidelines for auditing purposes.
Refer to the Security Bundle documentation for installation instructions and other details.
Define the Compliance Workflow
The following steps describe the basic secure development cycle:
- Developers check code out from source control.
- The code is modified and analyzed locally with the scope of analysis limited to the local changes. Depending on your implementation, local analysis may run a limited set of checkers.
- The code is checked into source control, triggering an automated build process.
- The entire codebase is analyzed during the build process.
- The results of the automated code analysis are sent to DTP.
- Depending on the implementation and business requirements, the CI process may or may not be gated. See Implementing Gates|#_Implementing_Gates
- The results are processed in DTP, where the team lead can use the Violations Explorer view to manually review violations and put them into remediation workflows or automate the process using DTP Enterprise Pack extensions and/or the DTP REST API.
- You can optionally create tickets in a tracking system from DTP. See Creating Tickets in External Systems (Optional)|#_Creating_Tickets_in
- Developers download the processed results ("findings") from DTP into their IDEs.
- Developers remediate the defects and repeat the process until the code meets the compliance policy.
You will need to determine the specifics for your organization, including:
- which security standard to use and which guidelines within the standard to follow
- how the checkers should be configured/parameterized
- what processes to automate
- whether additional test configuration variations will be needed
Implementing Gates
Gating is the concept of preventing the code from being promoted to the next stage of the release pipeline. Some organizations implement gates during check-in. In a safety-critical industry, gating the check-in may be an acceptable workflow, but we recommend implementing gates during the CI process. Doing so removes barriers to developer productivity and enables feedback (i.e., static analysis violations associated with meaningful information) to loop back to developers more quickly. Additionally, the CI build typically provides more context to enrich the information.
Feedback as Guidance for Developers
When viewed in the IDE or in DTP, code analysis violations include links to the documentation, which provides technical information and details about the potential impact of the programming patterns detected by the checkers. By providing detailed context about why violations are reported, developers gain a deeper understanding of the security issues associated with their code base. The guidance provided by the code analysis results, furthermore, is most effective when code analysis executes in the IDE before checking in the code.
Define Compliance Policy
Compliance in your organization may mean that no static analysis violations are allowed when checking code against a specific set of guidelines, such as OWASP Top 10. Compliance may also mean zero violations for only specific parts of the code . . . or for specific guidelines within a standard that you've determined to be critical to your project.
One or more of the following statements may serve as examples of an organization's compliance policy:
- 0 violations for injection flaw (A1:2017- Injection) checkers = compliant
- A percentage of all guideline checkers have 0 violations = compliant
- 0 violations of severe technical impact guidelines = compliant
- 0 deviations for severity 1 violations and only approved deviations for severity 2 violations = compliant
Start defining a compliance policy by first choosing a set of guidelines. You will need to review the available standards and determine which one is the best fit for your organization. Next, determine which guidelines within the standard are important and commit to complying with them. You will also need to determine in which circumstances your code will be allowed to deviate from the standard. Finally, you will also need to determine acceptable severity levels for violations.
Refer to your policy as you begin adapting Parasoft components to report and monitor compliance to your chosen standard.
Additional Considerations
The following sections introduce additional background and concepts for helping you define a policy.
Compliance Policy Vs. Compliance Goal
Your compliance policy should be a measurable and achievable plan for releasing software that conforms to a security standard. You can also define a compliance goal that strives for a higher degree of guideline conformance. Your compliance goal (like your compliance policy) is encapsulated in a code analysis configuration. The difference is that you expect to comply your compliance policy prior to release, whereas you expect to run your compliance goal configuration with acceptable outcomes at some time in the future. This topic is discussed in greater detail in the Desktop and Automation for Later (Optional) section.
How Parasoft Supports Security Compliance Initiatives
Parasoft supports compliance initiatives with advanced code analysis and reporting technologies. Parasoft tools check the code for specific patterns that are known to result in software defects. The checkers (also called static analysis rules) map to guidelines within a standard. More than one checker may be required to verify that the code meets a guideline. Conversely, more than one guideline may rely on a single checker. Refer to the Glossary of Terms for more detailed definitions of standards and guidelines.
The mapping between Parasoft checkers and coding guidelines may have an impact on how you define compliance in your organization. A checker may report violations for guidelines that are critical to your application, as well as guidelines that are less relevant. This is why the ability to suppress violations (deviate from the standard) is important. Deviations are discussed in greater detail in the Documenting Deviations section.|#_Documenting_Deviations
Parasoft DTP collects the data and outputs guideline-specific visualizations and reports for monitoring and demonstrating compliance. This is discussed in greater detail in the Monitoring and Demonstrating Compliance section.|#_Monitoring_and_Demonstrating
Parasoft checkers are identified according to the standard that they check against. For example, a checker that applies the CWE guideline "CWE-22: Improper Limitation of a Pathname to a Restricted Directory" has the ID "CWE.22.TDFNAMES."
Checkers are also categorized by severity. Parasoft tools rank the violations they report from severity 1 ("sev1") to severity 5 ("sev5") with sev1 violations being the most important. The expectation is that sev1, sev2, and sev3 checkers report defects that require remediation, whereas sev5 checkers are used as inspections checkers (sev4 violations are not used in the Parasoft security compliance workflow). Inspection checkers flag code that should be manually reviewed to ensure that the code is compliant with a guideline. See Inspection Rules for additional information.
Severity 1
Severity 2
Severity 3
Severity 4
Severity 5
Choose and Adapt a Test Configuration
Test configurations specify how Parasoft tools should execute their core features and functionality. They define the checkers that are enabled during code analysis, as well as configurations for checkers that support parameterization. Parasoft tools also ship with test configurations for executing unit tests, which specify how to instrument code for collecting coverage during test execution.
The following step are intended to help you refine your compliance plan and define the methods used to achieve compliance:
- choose a test configuration,
- execute the tool using the configuration,
- review the results,
- and adjust the configuration to your codebase and policy
Choosing a Test Configuration
The Parasoft Security Compliance Pack includes several test configurations that check compliance with the supported standards. When you install the Security Compliance Pack in DTP, the test configurations are automatically deployed to your DTP infrastructure. This enables you to centrally manage and distribute test configurations to your teams. Test configurations also ship with Parasoft tools for local execution, but using the test configurations stored in DTP enables you to uniformly apply checkers across teams (see Executing the Test Configuration).|#_Execute_and_Refine
Use the default test configurations as starting points and adapt them to meet your specific needs. Some checkers, for example, will need to be parameterized based on your code. Some checkers may not be a good fit for your codebase and should be disabled. If you do not need to handle input validation, for example, you may want to disable a checker that reports a violation when input validation isn't handled in a manner that's consistent with the guideline.
You can review the test configuration prior to execution and make some initial modifications, but fully understanding how to adjust the test configuration is an iterative process. Refer to the Updating Your Configuration section for information about modifying the test configuration.
Executing the Test Configuration
You can run the test configuration from the command line (e.g., as part of the automated CI process) or directly from within the IDE where the Parasoft tool is installed.
See Integration with Your Build Tool for command line execution.
Refer to the following documentation for details on running within the IDE:
- C/C++test Standard
- C/C++test Professional (Eclipse)
- C/C++test Professional (Visual Studio)
- dotTEST
- Jtest
Executing the test configuration on your complete project using the default settings may take a significant amount of time. One of the purposes of this step is to determine a baseline so that you can make decisions on how to balance resources to meet your compliance policy. You may determine that splitting checkers across several test configurations tuned for different milestones or development phases will be necessary.
By default, test configurations limit the code analysis results to 1000 violations per checker. If a rule is violating more than 1000 times, it means one of three things:
- The checker is incorrectly configured and should be parameterized.
- The code is poorly constructed. Additional training is required and adoption of the checker may need to be phased in.
- The checker is not applicable to your code and should be disabled.
To understand the total scope of work, you should disable the limit during the baselining phase and re-enable it after modifying your test configuration. Disabling the 1000-violation limit may result in significantly longer execution time.
Refer to the DTP documentation for details on how to change this setting.
Viewing Results
There are several ways to view code analysis results. By default, Parasoft tools output results to the <TOOL_INSTALL>/reports directory, but you can customize the directory, as well as format (HTML, PDF, XML) when you deploy your tool. You can open the report or load the results into the desktop instances of your Parasoft tools.
Viewing Reports in the Desktop
Refer to the documentation for details on viewing reports in the desktop:
- C/C++test Standard
- C/C++test Professional (Eclipse)
- C/C++test Professional (Visual Studio)
- dotTEST
- Jtest
If you integrated Parasoft with your CI tool, then, in addition to the HTML output, you can review results in one of the supported systems. Refer to the Parasoft Findings Plugin documentation for details.
Viewing Results in DTP
See the Monitoring and Demonstrating Compliance section for details about the available DTP interfaces for viewing static analysis violations.
How Many Violations is Too Many?
By default, the number of violations reported is limited to 1000 per checker. If a checker hits this limit or some lower threshold that fits your organization, the checker needs to be assessed. You should either configure/parameterize the checker, disable for old code, or disable and re-evaluated in the future.
In addition:
- A large number of sev1 or sev2 violations likely require immediate attention.
- A large number of sev3 violations may point to a mismatch in your organizations coding culture and the type of violations reported by some checkers.
- A low number of violations (e.g., fewer than 200) may still represent a problem, especially if they are sev1 or sev2 violations.|#_Executing_the_Test
Updating Your Configuration
Browse the results and update your test configuration based on whether or not you are going to fix the reported violations. Refer to the DTP documentation for details on how to update the test configuration.
Disable checkers that report violations that you are never going to fix. Suppress violations that are not acceptable in the reported instance but that you would otherwise fix (see Applying Suppressions). Refer to your compliance policy (see Define Compliance Policy) for guidance on which checkers to disable and which violations to suppress.
Some Parasoft checkers require parameterization, which is also configured in the test configuration. Parameterizable checkers have default values that you may need to change based on your code.
If the default severity associated with reported violations is too high or low, you can apply an updated rule map to change the severity—or even the category—to more accurately reflect how the coding pattern impacts your application. Refer to the Advanced Configuration and Strategies for information on changing checker severities and categories.
Applying Suppressions
Suppressions are one of the most important tools you can use when implementing a compliance initiative. A suppression is a code-level annotation that instructs Parasoft to continue checking for the pattern, but not to report it as a violation in the specific instance.
Instead of disabling a checker, for example, you may decide to suppress violations reported for modules associated with legacy code. In this way, the checker will stop reporting violations for code you are not going to touch but continue to report violations for new development.
Suppressions need to be documented in the final compliance report. See Documenting Deviations for details.
You can apply violations either in the desktop instance of your code analysis tool or in DTP.
Suppressing Violations in DTP
You can mark violations for suppression from DTP. The suppression is implemented on the next code analysis run. Refer to the DTP documentation for details on suppressing violations.
When static analysis violations are processed in DTP, desktop users can download violations, including suppressions, into their IDEs.
Suppressing Violations in Code
After a static analysis run, you can load the results into your IDE and suppress them using the GUI. In the phase described in the Monitoring and Demonstrating Compliance section, you will download the results from DTP. Processed results are referred to in the IDE as "findings."
Refer to the tool documentation for details:
- C/C++test Standard
- C/C++test Professional (Eclipse)
- C/C++test Professional (Visual Studio)
- dotTEST
- Jtest
Determine Your Remediation Strategy
After disabling checkers, applying suppressions, and making other changes to the Parasoft reporting mechanisms to encapsulate your compliance policy, you will likely still have violations that need to be fixed. See Remediation Workflow for details on how to prioritize and remediate violations.
Implement Your Compliance Strategy
At this point, your baseline infrastructure is set up and you should know how to handle exceptions. The code analysis tools should be configured to execute the test configuration during the CI process according to your workflow (e.g., nightly, hourly, triggered on check-in, etc.). The tools should also be configured to report analysis findings to DTP.
Developers working on the desktop, however, have different requirements as they run the test configuration locally on a day-to-day basis.
Regularly running code analysis on the desktop prevents defects from being injected into the code. Checked-out code, however, may refer to functions that are not within the local scope, resulting in additional static analysis violation noise. Additionally, some checkers perform data flow analysis, which simulates application execution to analyze possible paths. These checkers may report additional violations and take longer to execute. Analyzing legacy code, furthermore, can also produce noisy results at a time when developers are trying to remain productive.
Configure your desktop tools to execute a version of the baseline test configuration with the following adjustments:
- Flow analysis checkers should be disabled.
- Checkers that report sev3 and sev4 violations should be disabled. You may also consider disabling sev2 checkers if too many violations are still being reported until you've achieved compliance with sev1 violations.
- Inspection-type checkers, i.e., sev5, may also be executed on the desktop so that developers can review the feedback.
- The scope of analysis should be configured to analyze only new and checked-out code. Do not run analysis on legacy code unless you plan on fixing it.
- Reporting to DTP should be disabled. DTP should only be collecting analysis data from the CI runs.
Refer to the DTP documentation for information on how to duplicate and edit a test configuration to use for local analysis.
Refer to the documentation for your tool for details on how to use configurations stored on DTP:
- C/C++test Standard
- dotTEST
- Jtest
- C/C++test Professional (Eclipse)
- C/C++test Professional (Visual Studio)
Clean local code does not necessarily mean that the code will not trigger violations on the server. The automated build executes all checkers in the primary test configuration in the context of the scope of the entire code base. As a result, code that ran clean locally may result in violations when integrated with the rest of the build.
Achieving Your Compliance Goal
If you cannot achieve your compliance goal in the current phase of development, then you should split your code analysis checkers across multiple configurations for different phases of the development process.
For example, remediate sev1 violations in the first phase, sev2 in the next, and sev3 in the final phase. This enable your teams remain productive and agile by limiting the potential violations that must be remediated in each build to a manageable amount.
What-if Scenarios
Your compliance policy is measurable and achievable. Your compliance goal, however, encapsulates your long-term compliance objectives (see Compliance Policy Vs. Compliance Goal). You should define a test configuration that executes your compliance goal and occasionally run it as a way to understand the cost of conforming to additional guidelines specified in your chosen standard. You could also enable a selection of checkers to gain insight on extending your compliance policy to include one or more additional guidelines.
Regulatory Compliance
If your project is subject to an audit as part of a regulatory approval process, such as PCI-DSS or UL-2900, be aware that any defects uncovered in this phase may result in additional liability if they are not addressed.
- Create a test configuration that includes all checkers required for your currently defined security compliance initiative, as well as additional checkers you want to implement in the future.
- Create a tool configuration (settings.properties) file that your desktop and server tools can use to execute the correct test configuration. The tool configuration should report analysis findings to DTP in a different filter to avoid affecting the data associated with your current release.
- Add a Parasoft job to the continuous integration process to run the test configuration at an interval that makes sense for your organization.
Viewing Results in DTP
The Security Compliance Pack includes several dashboards optimized for viewing high-level information about the code analysis results in DTP. The dashboards include, for example, widgets that group violations according to risk and widgets that show changes in violations over time. Refer to the Security Compliance Pack documentation for details about the widgets and reports included with the compliance pack. Additional details are covered in Monitoring and Demonstrating Compliance. |#_Monitoring_and_Demonstrating
Remediation Workflow
The Violations Explorer view in DTP is an interface for reviewing and prioritizing findings, as well as applying remediation workflows. You can flag violations for suppression in subsequent runs (see Documenting Deviations), assign them to a team member, place them into external workflows, etc. Refer to the Violations Explorer view documentation for usage.|#_Documenting_Deviations
Some widgets in the compliance-specific dashboards shipped with the Security Bundle link directly the Violations Explorer, but many widgets link to intermediate reports showing details associated with a specific aspect of the data. Refer to Monitoring and Demonstrating Compliance for details about the dashboards, widgets, and reports.
Prioritize and Assign Findings
Prioritization in DTP means adding or updating the "priority" metadata associated with a finding. You can assign the following priorities:
- Critical
- High
- Medium
- Low
- Do not show
- Not defined
By default, priority is set to "Not defined," which can be changed in the Violations Explorer view. DTP also includes a REST API that enables you to programmatically control the metadata. You can also create an extension with the Extension Designer to automate prioritization when DTP collects the code analysis data. Refer to the API documentation (https://<YOUR_DTP_HOST>:<PORT>/grs/api) or the Extension Designer documentation for details.
There are several rationales for setting metadata:
Based on Authorship
In this approach, violations associated with code authored by specific team members can be prioritized for remediation. The focus here would be on potential defects introduced by outsourced, or third-party programmers, who may be a part of your software supply chain code, or on junior developers who need additional guidance.
Based on Severity
A consideration for this approach is that a high severity violation may normally be prioritized high but not in when it is reported in a part of the code with minimal security impact on the application. See Severities for details. |#_Severities
Based on Risk/Impact
The Risk/Impact field in DTP allows you to tag violations as extreme, high, moderate, and low. The default terminology used in this field is based on established risk score methods used in system engineering standards. You can also create custom tags that more accurately reflect conditions in your organization using the DTP REST API. Refer to the API documentation available at http://<host>:<port>/grs/api.
Based on Location in the Codebase
In many applications, certain parts of the codebase have a higher business value or represent greater risk than other parts. You can segment the code into resource groups and assign higher priorities to the findings associated with more valuable resources. Refer to the resource groups documentation for details.
Creating Tickets in External Systems (Optional)
Parasoft ships with out-of-the-box integration points with external ticketing systems (e.g. Jira and VersionOne), enabling you to create issues in the systems based on violations reported to DTP. Refer to the documentation for configuration and usage information.
You can also automate ticket creation either by using the REST API or by creating a custom workflow with Extension Designer. If you choose to fully automate ticket creation, make sure that you've fully tested your scripts, including error conditions, to avoid accidentally create thousands of tickets. If you choose to leverage this functionality, creating tickets manually is the recommended workflow.
Documenting Deviations
When you need to deviate from the security standard, you can apply a suppression in DTP or in the code from the desktop instance of your analysis tool. Suppressing a violation means that the defect pattern is acceptable in this specific instance and that you are going to ignore the violations reported by the tool for the foreseeable future.
A suppression applies to an instance of the violation, not to the checker, itself. The checker will continue reporting violations when the questionable pattern is detected in other parts of the code. If the checker truly does not apply to your application in any instance, disable it in the test configuration. Refer to the DTP documentation for instructions.
Suppressions are also important in terms of the review process associated with inspection rules. Violations reported by inspection rules are designed to trigger a manual review of the code. When the code is verified per the standard, the inspection rule can be suppressed with a rationale that serves as the documentation for the deviation. See Inspection Rules for additional information.
Documenting deviations is critical to any compliance initiative. When you choose to ignore certain violations that are in your stated compliance policy, you must provide justification. You can document deviations in DTP or in the IDE. Additionally, the Security Compliance artifact includes a deviations report that you can review as part of your development process. The report is available in HTML or PDF format.
Suppressing in DTP
Suppressing violations in DTP adds an instruction for the code analysis tool to apply the violation during the next code analysis run. The rationale for the suppression is part of your deviation documentation and must be concise. See the DTP documentation for instructions on suppressing violations in DTP.
Suppressing in the Desktop
Violations are also referred to as "findings" when they've been processed and tagged with analytics data. You can suppress individual instances of findings, all instances of a finding type in a file, or all findings in the file from the Findings view in C/C++test, dotTEST, and Jtest. Refer to the tool documentation for instructions:
- C/C++test Standard
- dotTEST
- Jtest
- C/C++test Professional (Eclipse)
- C/C++test Professional (Visual Studio)
Deviation Approval and Audit Workflow
Of course, no developer would suppress a violation simply because he or she didn't want to fix it, but you should implement a workflow for reviewing and approving suppressions, anyway, as part of your compliance policy. The most common way to review and approve suppressions is to leverage your existing code review process. Many organizations use third-party tools or native SCM functionality.
The Security Compliance Pack includes a Deviations Report that you can review in DTP. You should review the report as part of your code review process. You can export the report to PDF and check it into your SCM for auditing purposes. Refer to the documentation for the specific standard you intend to comply with for details:
DTP includes an Action field that you can leverage as part of the suppression audit process. This field includes the following default values:
- Fix
- None
- Other
- Reassign
- Review
- Suppress
You can set the action to Suppress and assign the violation to a reviewer who will agree and suppress the violation or make the case that the violation should not be suppressed in the comments. In this way, you create an audit trail in DTP around your suppressions. Refer to the Violation Explorer documentation for details.
High Deviation Counts
Coding standards are not perfect, one-size-fits-all sets of rules—which is why deviations are permissible in the first place. A high number of deviations, however, suggests that additional action should be taken.
The checker may simply need to be turned off in the test configuration (see Choose and Adapt a Test Configuration). The severity of the reported violations may need to be lowered (see Updating Rule Maps). The assignee or author may require additional training. The checker may be serving an "inspection rule" role (see Inspection Rules).
It is up to you to determine what is acceptable, but these aspects of your development process should be considered.
Inspection Rules
Checkers that report severity 5 (sev5) violations serve as inspection rules, which flag potential problems that require human oversight (also see Severities). When sev5 violations are reported in DTP, the action field should be set to Review and assigned to a team member for processing. |#_Severities
Inspection rules are noisy by nature. This is because they are intended to serve as a method calling attention to areas of the code that require manual peer review. If your security compliance strategy is to first prioritize compliance coverage, then you should disable sev5 checkers and focus on sev1, sev2, and sev3 violations. Inspection rules will eventually need to be re-enabled, however, because you will not be able to claim full compliance with guidelines that require manual inspection.
Importing Findings into the IDE
After processing the violations, developers can download them from DTP and load them into their IDEs. This workflow enables developers to hit the ground running on outstanding issues by immediately providing feedback as soon as they start their IDEs. The IDE should be configured to import only critical and high priority findings. Refer to the documentation for your tool for instructions on importing findings into the IDE:
- C/C++test Standard
- C/C++test Professional (Eclipse)
- C/C++test Professional (Visual Studio)
- dotTEST
- Jtest
Developers should treat the remediation of findings assigned to them as a regular part of their day-to-day workflow. They should also strive to check in code that does not trigger new violations so that each iteration brings the project closer to full compliance with the policy.
Monitor and Audit Compliance with Your Policy
Each standard supported by the Security Compliance Pack includes several components for monitoring and demonstrating compliance. Only violations reported by checkers in the compliance test configuration will appear in the compliance pack dashboards and reports. Refer to the documentation for each compliance artifact for details about adding compliance dashboards, viewing widgets, and viewing reports:
The dashboard templates shipped with the compliance pack include compliance specific widgets that show the compliance status for your project from several perspectives. The dashboards also leverage standard DTP widgets and reconfigure instances of the widgets to show data in context of the specific standard.
Compliance Reports
Each compliance artifact includes a primary report that you can export to PDF and use to demonstrate compliance during an audit, as well as several sub-reports that you can review to monitor compliance to your policy.
Compliance Percentage Widgets
The compliance percentage widgets provide at-a-glance status of the project and provide the main link to the compliance report.
Managing a Portfolio
Each Parasoft compliance artifact includes widgets specific to those standards. You can create a custom dashboard and add widgets configured to show data from each project using filters (see Creating and Managing Filters in the DTP documentation). Refer to the following DTP documentation for information about creating custom dashboards and manually configuring widgets:
- Adding a Dashboard
- Manually Adding CERT C Widgets
- Manually Adding the CERT C++ Widgets
- Manually Adding CWE Widgets
- Manually Adding OWASP Widgets
Advanced Compliance Monitoring Tools
The out-of-the-box configurations are intended to cover as many workflows as possible, but you can leverage additional functionality to further adapt the DTP solution to your needs.
Security Scoring
The compliance pack includes the Key Performance Indicator artifact that you can execute to calculate KPIs associated with the standard you've selected. KPIs are useful for comparing projects and for estimating risk and effort. This helps you understand the costs and effort associated with complying with your security guidelines. Refer to the following documentation for details on using the KPI functionality:
- Enabling KPI widgets for CERT C compliance
- Enabling KPI widgets for CERT C++ compliance
- Calculating CWE Security Impact
Resource Groups and Filters
DTP allows you to subset findings associated with a project by creating filters. For each project defined in DTP, a default filter with the same name of the project is created. Filters can have different run configurations, teams, and resource groups.
A resource group is a collection of resources (i.e., files and/or folders) defined by a set of one or more Ant file patterns. Resource groups enable more granular views of the data associated with a filter. After associating a resource group with a filter, the data presented in all widgets, reports, and explorer views for static analysis violations and metrics results will be narrowed according to the defined pattern.
Refer to the DTP documentation for details.
Advanced Configuration and Strategies
Implementing a security compliance initiative is not a one-size-fits-all process. The following adjustments may be required based on your specific needs. This section describes some of the advanced configurations and strategies that you can implement to help you improve your compliance processes.
Combining Security and Quality Checkers
You can combine quality and security checkers by enabling the quality checkers in your security compliance test configuration.
Be aware the adding quality checkers to your security test configuration may have unintended consequences. If your project is subject to safety-critical regulations, for example, and the quality checkers report violations that you had not planned on fixing, you may still be obligated to remediate those violations.
Be aware that violations associated with quality checkers will be included in the report generated by the tool. Security compliance reports, however, only contain output from the checkers associated with security guidelines.
Custom Checkers
If your code includes logic that is not covered by the checkers shipped with Parasoft tools, you can create custom checkers with Parasoft RuleWizard. No coding or knowledge of the parser is required to write or modify a rule, but expertise in understanding parse trees is advantageous.
You will need to add the <ruleId>.rule file to your tool's rules directory, enable the checker in the test configuration, and define it in the rule map. Refer to the DTP documentation for details.
Changing Severities
If the violation severity reported by a checker does not match your policy, you can modify the rule map in DTP to assign a new severity level, as well as change the checker ID or category. Refer to the DTP documentation for details.
Customizing the Compliance Pack
If you need to add or remove checkers that support a security guideline, you also need to modify the compliance profile. A profile is a set of configurations that perform custom calculations in DTP, such as calculating and reporting compliance statuses in DTP widgets.
A set of security compliance-related profiles are automatically deployed to your DTP environment when you install the Security Compliance Pack. The profiles serve as inputs for the compliance reports that you generate as part of a compliance audit. If you need to make adjustments, we recommend preserving the default profiles shipped with the compliance pack.
You can upload, export, and modify profiles using the DTP Enterprise Pack module. Refer to the Enterprise Pack documentation for general information about profiles.
Running What-if Scenarios
As you work toward your long-term compliance goal, you may want to incrementally enable additional checkers in your test configuration. Duplicate your primary test configuration and add one or more checkers. Before executing analysis, however, add a filter to your project and configure your tool to send the what-if execution results to the new filter. In this way, you are can keep exploratory analysis results separate from your official compliance data. Refer to the DTP documentation to learn more about filters.
The following sections describe the supported components for enabling Parasoft's Security Compliance solution.
Supported Languages
Out of the box, Parasoft supports the following languages:
- Java
- .NET-based languages
Parasoft supports several other programming languages via the Parasoft Multi-Language Pack:
- Android-based applications
- Go
- JavaScript
- Objective-C
- Python
- Ruby
- Scala
- Swift
- Typescript
Contact your Parasoft representative for Parasoft Multi-Language Pack download and license information.
DTP and Enterprise Pack 5.4.3
DTP and Enterprise Pack 5.4.2
Parasoft tools
C/C++test 10.4.2
Continuous integration
Parasoft can report static analysis violations in the following CI systems:
Source control
Refer to the tool documentation for supported SCMs:
DTP and Enterprise Pack 5.4.1
Parasoft tools
C/C++test 10.4.1
Continuous integration
Parasoft can report static analysis violations in the following CI systems:
Source control
Refer to the tool documentation for supported SCMs:
Glossary of Terms
The following terms are used throughout this guide.
Also sometimes called 'rules', checkers are pieces of software that check the correctness of code against a specific programming pattern.
Compliance Goal
A compliance goal is a long-term plan for conforming to a software development standard. In contrast to a Compliance Policy, a compliance goal is not generally achievable within the current software release. Compliance goals are encapsulated in a code analysis configuration that, when executed by a Parasoft tool, reports violations that you plan to remediate in a future release.
Compliance Policy
A compliance policy is a measurable and achievable plan for releasing software that conforms to a software development standard. Compliance policies are encapsulated in a code analysis configuration that, when executed by a Parasoft tool, should report no violations.
The degree to which the code meets the stated goals of a policy or guideline within a standard. When no static analysis violations are reported, the code is in compliance, regardless of how many checkers are enabled. It is possible for the code to be 100% in compliance with a policy, but fail to reach even partial conformance with a standard if, for example, the policy specifies that only one guideline from the standard should be followed.
Conformance is a measure of how completely the code is in compliance with the guidelines within a standard. To be 100% conformant, the code must be in compliance with all guidelines specified in the standard.
Internationally, the underlying concepts associated with "conformance" and "nonconformance" are referred to as "conformity" and "non-conformity." Adhering to the procedures you've defined is conformity or conformance, whereas not adhering to them is nonconformity or nonconformance. Procedures that meet federal (external) requirements are in compliance, whereas procedures that do not meet requirements are in noncompliance.
See Suppression
See Violations.
A guideline is a specific rule or principle within a standard that provides guidance on a single programming topic. For example, the OWASP Top 10 standard includes the following guideline:
"A1:2017-Injection: Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker's hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization."
Depending on the standard, guidelines may include example code, risk impact, and other information that help you determine if specific guidelines should be followed for your project.
A rule in Parasoft refers to a code analysis Checker. Others may use the term to mean Guideline.
A standard is a set of related programming guidelines, such as CERT C, CWE 3.2, and OWASP Top 10.
A suppression is a code-level annotation that instructs Parasoft to continue checking for the pattern, but not to report it as a violation in the specific instance. When a violation is marked with a suppression in a compliance context, it is referred to as a deviation from the standard and must be documented with a justification for allowing the violation to remain.
Parasoft refers to the raw programming errors reported by code checkers as "violations" of the rules codified by the checkers. Parasoft attaches additional information about the violations, such as code authorship, build information, etc., as part of the reporting process. The processes violations are referred to as "findings." Findings can refer to static analysis violations that appear in the code analysis report or violations that have been processed by DTP and downloaded to the developers' IDEs. Subtle differences exist, but violations and findings (as well as other terminology used throughout the software testing industry, including "errors" and "defects") are often used interchangeably.

subset: commoncrawl


text:
Cole: Obama 'commendably cautious'
Rep. Tom Cole on Friday praised President Barack Obama for being "commendably cautious" about potential military action in Syria against the Islamic State of Iraq and the Levant.
Appearing on MSNBC, the Oklahoma Republican downplayed criticism that White House lacks a plan to combat ISIL militants, a concern stemming from a White House press briefing Obama gave the day before.
"I think the elements of a strategy are there," the House Defense Appropriations Subcommittee member said. "Look, the president's made clear and, I think, appropriate we're talking about airstrikes at some point," as well as special operators, aid, training and consolidating allies in the Middle East.
The president has received backlash for comments he made Thursday about ISIL, the group that has swept across much of eastern Syria and northern and central Iraq. The Obama administration, which launched airstrikes against ISIL targets in Iraq, has said it is considering airstrikes against the group in Syria. On Thursday, the president said: "I don't want to put the cart before the horse. We don't have a strategy yet," remarks that drew criticism from Republicans and conservative media outlets who have long accused Obama of being weak on foreign policy and disengaged from the world.
White House press secretary Josh Earnest and Pentagon press secretary Rear Adm. John Kirby have since clarified that the president was speaking specifically about military action against ISIL targets in Syria, and that the White House has long had a comprehensive strategy against the group in Iraq.
On Friday, Cole said the president is taking an appropriate approach to a tricky problem in Syria, where ISIL forces have been fighting against Syrian President Bashar Assad, who, the U.S. has said, used chemical weapons against his own people.
"I think the president is being commendably cautious here about being involved in the middle of the Syrian civil war," he said, adding that he doesn't necessarily think the U.S. has a "responsibility" in Syria beyond targeting ISIL.
Cole, a close ally of House Speaker John Boehner, said Obama must come to Congress for any significant military action in Syria. "Congress has to be absolutely central," he said.


text:
Beat you to it. :friendly_wink:
PG, Would a photocopy of trust documents be valid or would duplicates each with original signatures be required?
Type: Posts; User: adjusterjack; Keyword(s):
Beat you to it. :friendly_wink:
PG, Would a photocopy of trust documents be valid or would duplicates each with original signatures be required?
Nothing. He's dead.
But if you are asking what he can do while he's alive he can name a trustee who is not a beneficiary and leave the original trust documents with that person.
Well, $2600 is hardly enough for the consequences of bankruptcy.
Do you have a job? One that's worth keeping? If yes, call the lender and see if you can get a payment plan that's equal to the...
None of that means anything. You still owe the money. A charge-off is an accounting thing that allows the lender to take a tax write-off for a bad debt. The lender can still pursue the debt and if...
Contact the Ohio Department of Labor:
Ask if there are any laws or rules about a former employer having to replace a lost...
And by making a will that spells out the disposition of personal property.
And by listing a beneficiary on accounts.
Yes, your conversion to Roth is taxable (without penalty after 59 1/2). The idea, though, is that your investment earnings that flows into the new Roth is non taxable after 5 years for each...
Do both. Tax deferred when your income is high. Upon retirement, convert portions to Roth (or cash) each year to minimize income taxes.
Check your sales contract to see if it has a bilateral attorney fee provision. If it does, you might be able to recover attorney fees. The best person to ask, of course, is your attorney.
You get the $500k exclusion. The following is right out of IRS Publication 523 Page 3 Ownership
Determine whether you meet the ownership require-ment.If you owned the home for at least 24 months...
An attorney who participates here under the name Taxing Matters has written the following about LLCs:
The LLC form of business, like the corporation, protects the owners of the business from...
Same answer I gave you last April.
I'm not seeing any benefit from an LLC either. I've owned rental homes without one.
Why do you think you need one?
You didn't answer the question then....
I think you meant that for the snow thread, not this one.
I checked the DFAS website briefly and couldn't find anything about an appeal for denial of benefits. You might want to spend some time drilling through it or ask a rep about it.
I seriously doubt that there is any statute that addresses how one clears his driveway of snow.
This is either an intentional or negligent act for which you can sue under common law if you...
Reported for deletion.
State court if the business has substantial presence in your state. If not you are likely to have to file in the state where the business is located.
If you are in CT, here's the applicable law:...
Of course you have a right to "request." Go ahead and request and see how it goes.
I don't know. Pay what they say. Get a tax attorney. Doesn't seem that you have many options.
Let this be...
Are you going to post the video as a public service or do you expect to make money from it?
The first link you provided says:
The second link that "attaches strings" is the "unless...
I'm no expert but I think it means that you can't use the CDC logo by itself. For example, you have a company name with the initials CDC, you cannot use the design for your logo.
Reproducing the...
You have taken that sentence out of context and it's obviously not a word for word quotation.
Provide a link to that limitation if you want comments on what it actually says.
There is nothing illegal about it. You just don't want to accept it.
Oh gee. Another unhappy teenager. If the abuse is that bad, call child protective services and you might be removed from the home.
Otherwise stick it out until you are 18. Then you'll be an adult...
First thing you have to understand is that Progressive is not your insurance company and has a contractual obligation to protect its own insured, even when its insured is at fault.
When more than...


text:
Antidepressant Trazodone In Naval Yard Gun Massacre
by Peter R. Breggin, MD
September 18, 2013
This brief analysis is offered in response to information that the Navy Yard mass murderer, Aaron Alexis, was taking the antidepressant trazodone. Alexis was reportedly started on trazodone for sleep on August 23, 2013 at the Veterans Administration (VA) clinic in Providence and refilled on August 28 at the VA in Washington, DC. Twenty days later, on September 16, he committed the violent assaults. Severe adverse drug reactions such as suicide and violence typically occur in this relatively short time span after starting an antidepressant. Individuals with a known history of violence like Alexis are at even higher risk of being driven to more extreme violence by exposure to antidepressant drugs.
Antidepressants can cause a broad range of stimulating amphetamine-like adverse drug effects that will then cause or contribute to violence. The official FDA-approved label for trazodone lists the following stimulating effects: "anxiety, agitation, panic attacks, insomnia, irritability, hostility, aggressiveness, impulsivity, akathisia (psychomotor restlessness), hypomania and mania."
Although commonly used as a sleeping pill, trazodone nonetheless can be very stimulating for some patients. It has higher reported rates than other antidepressants such as paroxetine (Paxil) and sertraline (Zoloft) for causing anxiety, nervousness, excitement, and hypomania, which are risk factors for causing violence. Trazodone blocks the removal of serotonin from the synapse in the same manner as the SSRIs (selective serotonin reuptake inhibitors) like Prozac (fluoxetine), Paxil and Zoloft; and therefore has similar dangerous effects.
The trazodone Medication Guide, found toward the back of the FDA-approved label, warns about patients "acting aggressive, being angry or violent." It also warns about "Acting on dangerous impulses" while taking trazodone.
With the caveat that new information will continue to come forth about Aaron Alexis' life, as well the caveat that I have no access to his medical records—trazodone must be weighed and considered as a possible if not probable cause or contributing factor to worsening Alexis' violence tendencies and pushing him over into a murderous rampage.
Medication history taken from the New York Times (toward the end of the article):
The FDA-Approved Label (also called Complete Prescribing Information) for trazodone can be obtained on the Internet at Drugs.Com, FDA.gov, or other sources.
For scientific details and case studies concerning medication-induced violence, See Peter R. Breggin, MD. Medication Madness: The Role of Psychiatric Drugs in Cases of Violence, Suicide and Crime. New York: St. Martin's Press, 2008.


text:
Storm Lakes, Photo Gallery, Indian Peaks Wilderness Area, Colorado
Storm Lakes
Indian Peaks Wilderness Area
The Storm Lakes are located above Jasper Lake in the Indian Peaks Wilderness. No trail reaches the lakes, but a challenging cross-country route follows Jasper Creek from Jasper Lake to its source at Storm Lake, and up to Upper Storm Lake in a deep bowl under the Continental Divide.
|Related Trails:
|Storm Lakes
Storm Lake (11,415') is located approximately .5 miles and 600' above Jasper Lake, and forms the headwaters of Jasper Creek
Upper Storm Lake (11,965') is located approximately 1.5 miles and 1150' above Jasper Lake in a small, deep cirque just below the Continental Divide
Jasper Lake, which remains in view much of the way, is a reservoir whose rights are owned by Caribou Ranch
The off-trail route to Storm Lake begins from the NW side of Jasper Lake, where you'll follow the inlet through treeline
The route closely skirts several tarns and countless cascades through a relatively narrow valley
Storm Lake forms Jasper Creek, which flows through Jasper Lake Reservoir into South Fork Middle Boulder Creek
The route runs through and around several large ponds on the NW side of Storm Lake before pitching steeply up a rock face into the upper valley
The 1.5 mile - 1150' climb from Jasper to Upper Storm Lake eases briefly across several wide benches between steep pitches and scrambles
The narrow valley leaves little room to maneuver around tarns, snowfields, streams and willow patches
The steep-walled Jasper Creek valley blocks your view of incoming weather, and storms can form quickly overhead - get an early start and expect slower travel times than distances may indicate
Parry's Primrose, which favors moist soil and is found in abundance along the route's many streams, is named after Charles C. Parry, an English physician who was the first botanist for the US Department of Agriculture
Creeks run under several wide snowfields and hollow out unstable snow bridges over their path
Though steep grades pose the biggest overall challenge, negotiating thick willow is a constant battle
Poles and traction devices can be very helpful on steep snowfields between lakes


text:
About this file
This is the perfect template for any game related layout or for a clan website. Enjoy
If you are thinking about launching a website for your game plans then you might be interested in this layered PSD layout with plenty of eye catching features in the design.
You will download 4 PSD files containing two versions of the layout in two different colors ( Green and blue ) Each PSD file has around 200 layers each. You can play as you want with this file, and change it for your own needs.
Each color has two pages: Home page Inner page
All layers have the layer styles attached and you can customize as you want.
The font i have used in Myriad Pro ( included in any windows installation )


text: Commencement 2012 The May 10 ceremonies at Pacific Lutheran Theological Seminary's Chapel of the Cross recognized 62 graduates who completed their degrees in Fall 2011 or Spring 2012. Thirty-six students graduated with a Master of Arts degree, five received a Master of Arts with a concentration in Biblical Languages, and twenty-one received the Doctor of Philosophy degree. Graduates are listed by degree and include their thesis title, area of study or school of affiliation, committee members, and thesis abstract; language specialization is noted for MABL graduates in lieu of thesis information. View photos on... GTU AlumsGeneralAlumniEventsCommencement


text:
Our history
We've moved the world to protect animals for more than 50 years.
We're proud of our past
We became World Animal Protection in June 2014. But while our name has changed, our determination to protect animals remains as strong as ever. We've grown, and so has our influence. And, just like our supporters worldwide, we know change is always possible – because we've been transforming animals' lives since 1950.
World Animal Protection: key dates
1950 The World Federation for the Protection of Animals (WFPA) is formed
1959 The International Society for the Prevention of Cruelty to Animals (ISPA) is formed
1981 WFPA and ISPA merge to become WSPA – the World Society for the Protection of Animals
2014 We become World Animal Protection.
World Animal Protection in New Zealand
With an office in Auckland, since 2003 World Animal Protection in New Zealand has been fundraising and campaigning on a range of important issues, including lobbying the government for stronger animal welfare laws.
We are a member of the National Animal Welfare Emergency Management (NAWEM) Liaison Group, Animal Behaviour and Welfare Consultative Committee (ABWCC) and the New Zealand Companion Animal Council (NZCAC). We work closely with the Ministry of Civil Defence and Emergency Management, the Department of Conservation and the Ministry for Primary Industries to improve the welfare of all animals in New Zealand.
A history of protecting animals everywhere
We've always moved wherever the need for animal protection is greatest – from treating more than 70,000 animals following the Haiti earthquake in 2010, to training vets in Thailand, to ending bear dancing across India in 2012, to investigating animal trafficking in El Salvador. And as we've grown, we've focused on protecting more animals in more places. Today, we have regional hubs in Africa, Asia, Europe, Latin America and North America, and offices in 15 countries. Find out more about our work worldwide.
A history of disaster work
Ever since 'Operation Gwamba', when we rescued 10,000 animals from floodwaters in Suriname in 1964, we've protected hundreds of thousands of animals in disasters. We've responded to earthquakes, tsunamis, typhoons, tornadoes, volcano eruptions, cyclones and shipwrecks. We've saved animals in conflicts from Bosnia to Rwanda to Afghanistan. And, today, we move faster than ever to protect animals when disaster strikes. See how we save animals in disasters.
A history of campaigning
We've campaigned for lasting change for decades. Launched in 1985, our campaign against bullfighting moved almost 50 cities in France and Spain to ban bullfighting. In the same decade, India banned the trade in frogs' legs after six years of WSPA campaigning – saving more than 30 million frogs annually. And in the 1990s, our Libearty campaign helped to outlaw bear dancing in Greece, Turkey and most of India. Today, we keep piling on the pressure – add your voice to help protect animals.
A history of global action
We've moved international organisations to protect animals for many years. As WSPA, we began lobbying the EU in the 1980s, were given consultative status at the UN in 1981 and by the 1990s had been represented at the Council of Europe. And we're now the only animal protection organisation to regularly address the UN.
We're proud of our past and excited about our future – join us to help move the world to protect animals.


text:
Sorry, there has been an error or the page content or item you requested could not be found. This may be because information has expired for security reasons, a long period of browser inactivity or because of a temporary site or internet error. Please click back and try again. If the problem persists, please navigate to one of the below websites.
Our photographer representation service, Global Assignment features a roster of acclaimed international photographers chosen for the unique vision and creativity they bring to their work - and yours. And to make your commission as easy as possible, we can oversee every element, with our photographers, reps and in-house production teams handling everything from concept to post-production.
Contact your nearest Global Assignment office for more information.
Or visit our site to find a photographer for your project.
Reportage is home to some of the world's most powerful photojournalism, created by award-winning international photographers and emerging new talent. You'll find authentic images from in-depth features that address the major issues of our day. And all photographers are available for assignment work, bringing their unique perspectives to your commissioned project.
Contact your Reportage agent or editor for more information.
Or visit our site to find a photographer or browse images.